Method and apparatus for requesting resource for control element transmission in a wireless communication system

ABSTRACT

A method and apparatus are disclosed from the perspective of a UE, wherein the UE is allocated with multiple SR configurations by a network node. In one embodiment, the method includes the UE triggering a MAC control element if a timer expires. The method also includes the UE triggering a SR for the MAC control element. The method also includes the UE transmitting the SR based on a first SR configuration of the multiple SR configurations, wherein the first SR configuration is associated with a highest priority logical channel having data available for transmission when the MAC control element is triggered.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is continuation of U.S. patent application Ser.No. 15/963,313, filed Apr. 26, 2018, which claims priority to and thebenefit of U.S. Provisional Patent Application Ser. No. 62/490,072,filed Apr. 26, 2017, and U.S. Provisional Patent Application Ser. No.62/519,718, filed Jun. 14, 2017; with the entire disclosures of eachreferenced application incorporated fully herein by reference.

FIELD

This disclosure generally relates to wireless communication networks,and more particularly, to a method and apparatus for requesting resourcecontrol element transmission in a wireless communication system.

BACKGROUND

With the rapid rise in demand for communication of large amounts of datato and from mobile communication devices, traditional mobile voicecommunication networks are evolving into networks that communicate withInternet Protocol (IP) data packets. Such IP data packet communicationcan provide users of mobile communication devices with voice over IP,multimedia, multicast and on-demand communication services.

An exemplary network structure is an Evolved Universal Terrestrial RadioAccess Network (E-UTRAN). The E-UTRAN system can provide high datathroughput in order to realize the above-noted voice over IP andmultimedia services. A new radio technology for the next generation(e.g., 5G) is currently being discussed by the 3GPP standardsorganization. Accordingly, changes to the current body of 3GPP standardare currently being submitted and considered to evolve and finalize the3GPP standard.

SUMMARY

A method and apparatus are disclosed from the perspective of a UE (UserEquipment), wherein the UE is allocated with multiple SR (SchedulingRequest) configurations by a network node. In one embodiment, the methodincludes the UE triggering a MAC (Medium Access Control) control elementif a timer expires. The method also includes the UE triggering a SR forthe MAC control element. The method also includes the UE transmittingthe SR based on a first SR configuration of the multiple SRconfigurations, wherein the first SR configuration is associated with ahighest priority logical channel having data available for transmissionwhen the MAC control element is triggered.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a wireless communication system according toone exemplary embodiment.

FIG. 2 is a block diagram of a transmitter system (also known as accessnetwork) and a receiver system (also known as user equipment or UE)according to one exemplary embodiment.

FIG. 3 is a functional block diagram of a communication system accordingto one exemplary embodiment.

FIG. 4 is a functional block diagram of the program code of FIG. 3according to one exemplary embodiment.

FIG. 5 is a reproduction of FIG. 6.1.3.1-1 of 3GPP TS 36.321 V14.2.0.

FIG. 6 is a reproduction of FIG. 6.1.3.1-2 of 3GPP TS 36.321 V14.2.0.

FIG. 7 is a reproduction of Table 6.1.3.1-1 of 3GPP TS 36.321 V14.2.0.

FIG. 8 is a reproduction of Table 6.1.3.1-2 of 3GPP TS 36.321 V14.2.0.

FIG. 9 is a reproduction of FIG. 6.1.3.1a-1 of 3GPP TS 36.321 V14.2.0

FIG. 10 is a reproduction of FIG. 6.1.3.1a-2 of 3GPP TS 36.321 V14.2.0.

FIG. 11 is a diagram according to one exemplary embodiment.

FIG. 12 is a diagram according to one exemplary embodiment.

FIG. 13 is a diagram according to one exemplary embodiment.

FIG. 14 is a diagram according to one exemplary embodiment.

FIG. 15 is a diagram according to one exemplary embodiment.

FIG. 16 is a diagram according to one exemplary embodiment.

FIG. 17 is a diagram according to one exemplary embodiment.

FIG. 18 is a diagram according to one exemplary embodiment.

FIG. 19 is a diagram according to one exemplary embodiment.

FIG. 20 is a diagram according to one exemplary embodiment.

FIG. 21 is a diagram according to one exemplary embodiment.

FIG. 22 is a diagram according to one exemplary embodiment.

FIG. 23 is a diagram according to one exemplary embodiment.

FIG. 24 is a diagram according to one exemplary embodiment.

FIG. 25 is a diagram according to one exemplary embodiment.

FIG. 26 is a diagram according to one exemplary embodiment.

FIG. 27 is a diagram according to one exemplary embodiment.

FIG. 28 is a diagram according to one exemplary embodiment.

FIG. 29 is a diagram according to one exemplary embodiment.

FIG. 30 is a diagram according to one exemplary embodiment.

FIG. 31 is a diagram according to one exemplary embodiment.

FIG. 32 is a diagram according to one exemplary embodiment.

FIG. 33 is a diagram according to one exemplary embodiment.

FIG. 34 is a diagram according to one exemplary embodiment.

FIG. 35 is a flow chart according to one exemplary embodiment.

FIG. 36 is a flow chart according to one exemplary embodiment.

FIG. 37 is a flow chart according to one exemplary embodiment.

FIG. 38 is a flow chart according to one exemplary embodiment.

FIG. 39 is a flow chart according to one exemplary embodiment.

FIG. 40 is a flow chart according to one exemplary embodiment.

FIG. 41 is a flow chart according to one exemplary embodiment.

FIG. 42 is a flow chart according to one exemplary embodiment.

FIG. 43 is a flow chart according to one exemplary embodiment.

FIG. 44 is a flow chart according to one exemplary embodiment.

FIG. 45 is a flow chart according to one exemplary embodiment.

FIG. 46 is a flow chart according to one exemplary embodiment.

DETAILED DESCRIPTION

The exemplary wireless communication systems and devices described belowemploy a wireless communication system, supporting a broadcast service.Wireless communication systems are widely deployed to provide varioustypes of communication such as voice, data, and so on. These systems maybe based on code division multiple access (CDMA), time division multipleaccess (TDMA), orthogonal frequency division multiple access (OFDMA),3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A orLTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultra MobileBroadband), WiMax, or some other modulation techniques.

In particular, the exemplary wireless communication systems devicesdescribed below may be designed to support one or more standards such asthe standard offered by a consortium named “3rd Generation PartnershipProject” referred to herein as 3GPP, including: TR 38.913 V14.1.0,“Study on Scenarios and Requirements for Next Generation AccessTechnologies”; TS 36.300 V14.2.0, “Evolved Universal Terrestrial RadioAccess (E-UTRA) and Evolved Universal Terrestrial Radio Access Network(E-UTRAN); Overall description; Stage 2”; TS 36.321 V14.2.0, “EvolvedUniversal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC)protocol specification”; TS 36.331 V14.2.0, “Evolved UniversalTerrestrial Radio Access (E-UTRA); Radio Resource Control (RRC);Protocol specification”; TS 38.804 v14.0.0, “Study on New Radio AccessTechnology; Radio Interface Protocol Aspects”; R2-1703796, “Report fromNR/LTE Break-Out Session (UP NR, FeD2D, Wearables, Rel-14 corrections)”;and R2-1704030, “Report from LTE Break-Out session”, Vice-Chair(InterDigital). The standards and documents listed above are herebyexpressly incorporated by reference in their entirety.

FIG. 1 shows a multiple access wireless communication system accordingto one embodiment of the invention. An access network 100 (AN) includesmultiple antenna groups, one including 104 and 106, another including108 and 110, and an additional including 112 and 114. In FIG. 1, onlytwo antennas are shown for each antenna group, however, more or fewerantennas may be utilized for each antenna group. Access terminal 116(AT) is in communication with antennas 112 and 114, where antennas 112and 114 transmit information to access terminal 116 over forward link120 and receive information from access terminal 116 over reverse link118. Access terminal (AT) 122 is in communication with antennas 106 and108, where antennas 106 and 108 transmit information to access terminal(AT) 122 over forward link 126 and receive information from accessterminal (AT) 122 over reverse link 124. In a FDD system, communicationlinks 118, 120, 124 and 126 may use different frequency forcommunication. For example, forward link 120 may use a differentfrequency then that used by reverse link 118.

Each group of antennas and/or the area in which they are designed tocommunicate is often referred to as a sector of the access network. Inthe embodiment, antenna groups each are designed to communicate toaccess terminals in a sector of the areas covered by access network 100.

In communication over forward links 120 and 126, the transmittingantennas of access network 100 may utilize beamforming in order toimprove the signal-to-noise ratio of forward links for the differentaccess terminals 116 and 122. Also, an access network using beamformingto transmit to access terminals scattered randomly through its coveragecauses less interference to access terminals in neighboring cells thanan access network transmitting through a single antenna to all itsaccess terminals.

An access network (AN) may be a fixed station or base station used forcommunicating with the terminals and may also be referred to as anaccess point, a Node B, a base station, an enhanced base station, anevolved Node B (eNB), or some other terminology. An access terminal (AT)may also be called user equipment (UE), a wireless communication device,terminal, access terminal or some other terminology.

FIG. 2 is a simplified block diagram of an embodiment of a transmittersystem 210 (also known as the access network) and a receiver system 250(also known as access terminal (AT) or user equipment (UE)) in a MIMOsystem 200. At the transmitter system 210, traffic data for a number ofdata streams is provided from a data source 212 to a transmit (TX) dataprocessor 214.

In one embodiment, each data stream is transmitted over a respectivetransmit antenna. TX data processor 214 formats, codes, and interleavesthe traffic data for each data stream based on a particular codingscheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot datausing OFDM techniques. The pilot data is typically a known data patternthat is processed in a known manner and may be used at the receiversystem to estimate the channel response. The multiplexed pilot and codeddata for each data stream is then modulated (i.e., symbol mapped) basedon a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM)selected for that data stream to provide modulation symbols. The datarate, coding, and modulation for each data stream may be determined byinstructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TXMIMO processor 220, which may further process the modulation symbols(e.g., for OFDM). TX MIMO processor 220 then provides N_(T) modulationsymbol streams to N_(T) transmitters (TMTR) 222 a through 222 t. Incertain embodiments, TX MIMO processor 220 applies beamforming weightsto the symbols of the data streams and to the antenna from which thesymbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol streamto provide one or more analog signals, and further conditions (e.g.,amplifies, filters, and upconverts) the analog signals to provide amodulated signal suitable for transmission over the MIMO channel. N_(T)modulated signals from transmitters 222 a through 222 t are thentransmitted from N_(T) antennas 224 a through 224 t, respectively.

At receiver system 250, the transmitted modulated signals are receivedby N_(R) antennas 252 a through 252 r and the received signal from eachantenna 252 is provided to a respective receiver (RCVR) 254 a through254 r. Each receiver 254 conditions (e.g., filters, amplifies, anddownconverts) a respective received signal, digitizes the conditionedsignal to provide samples, and further processes the samples to providea corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the N_(R) receivedsymbol streams from N_(R) receivers 254 based on a particular receiverprocessing technique to provide N_(T) “detected” symbol streams. The RXdata processor 260 then demodulates, deinterleaves, and decodes eachdetected symbol stream to recover the traffic data for the data stream.The processing by RX data processor 260 is complementary to thatperformed by TX MIMO processor 220 and TX data processor 214 attransmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use(discussed below). Processor 270 formulates a reverse link messagecomprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of informationregarding the communication link and/or the received data stream. Thereverse link message is then processed by a TX data processor 238, whichalso receives traffic data for a number of data streams from a datasource 236, modulated by a modulator 280, conditioned by transmitters254 a through 254 r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system250 are received by antennas 224, conditioned by receivers 222,demodulated by a demodulator 240, and processed by a RX data processor242 to extract the reserve link message transmitted by the receiversystem 250. Processor 230 then determines which pre-coding matrix to usefor determining the beamforming weights then processes the extractedmessage.

Turning to FIG. 3, this figure shows an alternative simplifiedfunctional block diagram of a communication device according to oneembodiment of the invention. As shown in FIG. 3, the communicationdevice 300 in a wireless communication system can be utilized forrealizing the UEs (or ATs) 116 and 122 in FIG. 1 or the base station (orAN) 100 in FIG. 1, and the wireless communications system is preferablythe LTE system. The communication device 300 may include an input device302, an output device 304, a control circuit 306, a central processingunit (CPU) 308, a memory 310, a program code 312, and a transceiver 314.The control circuit 306 executes the program code 312 in the memory 310through the CPU 308, thereby controlling an operation of thecommunications device 300. The communications device 300 can receivesignals input by a user through the input device 302, such as a keyboardor keypad, and can output images and sounds through the output device304, such as a monitor or speakers. The transceiver 314 is used toreceive and transmit wireless signals, delivering received signals tothe control circuit 306, and outputting signals generated by the controlcircuit 306 wirelessly. The communication device 300 in a wirelesscommunication system can also be utilized for realizing the AN 100 inFIG. 1.

FIG. 4 is a simplified block diagram of the program code 312 shown inFIG. 3 in accordance with one embodiment of the invention. In thisembodiment, the program code 312 includes an application layer 400, aLayer 3 portion 402, and a Layer 2 portion 404, and is coupled to aLayer 1 portion 406. The Layer 3 portion 402 generally performs radioresource control. The Layer 2 portion 404 generally performs linkcontrol. The Layer 1 portion 406 generally performs physicalconnections.

3GPP standardization activities on next generation (i.e., 5G) accesstechnology have been launched since March 2015. The next generationaccess technology aims to support the following three families of usagescenarios for satisfying both the urgent market needs and the morelong-term requirements set forth by the ITU-R IMT-2020:

-   -   eMBB (enhanced Mobile Broadband)    -   mMTC (massive Machine Type Communications)    -   URLLC (Ultra-Reliable and Low Latency Communications).

An objective of the 5G study item on new radio access technology is toidentify and develop technology components needed for new radio systemswhich should be able to use any spectrum band ranging at least up to 100GHz. Supporting carrier frequencies up to 100 GHz brings a number ofchallenges in the area of radio propagation. As the carrier frequencyincreases, the path loss also increases.

Scheduling Request (SR) procedure and Buffer Status Report (BSR)procedure are designed for UE to request uplink resource. On the otherhand, Sidelink Buffer Status Report procedure is designed for UE torequest dedicated sidelink resource. Since Sidelink BSR or BSR shall betransmitted to base station, the UE will trigger SR to request uplinkresource for transmitting Sidelink BSR or BSR if needed. Detailprocedures are described in 3GPP TS 36.321 as follows:

5.4.4 Scheduling Request

The Scheduling Request (SR) is used for requesting UL-SCH resources fornew transmission. When an SR is triggered, it shall be considered aspending until it is cancelled. All pending SR(s) shall be cancelled andsr-ProhibitTimer shall be stopped when a MAC PDU is assembled and thisPDU includes a BSR which contains buffer status up to (and including)the last event that triggered a BSR (see subclause 5.4.5), or, if allpending SR(s) are triggered by Sidelink BSR, when a MAC PDU is assembledand this PDU includes a Sidelink BSR which contains buffer status up to(and including) the last event that triggered a Sidelink BSR (seesubclause 5.14.1.4), or, if all pending SR(s) are triggered by SidelinkBSR, when upper layers configure autonomous resource selection, or whenthe UL grant(s) can accommodate all pending data available fortransmission.If an SR is triggered and there is no other SR pending, the MAC entityshall set the SR_COUNTER to 0.As long as one SR is pending, the MAC entity shall for each TTI:

-   -   if no UL-SCH resources are available for a transmission in this        TTI:        -   if the MAC entity has no valid PUCCH resource for SR            configured in any TTI and if rach-Skip for the MCG MAC            entity or rach-SkipSCG for the SCG MAC entity is not            configured: initiate a Random Access procedure (see            subclause 5.1) on the SpCell and cancel all pending SRs;        -   else if the MAC entity has at least one valid PUCCH resource            for SR configured for this TTI and if this TTI is not part            of a measurement gap or Sidelink Discovery Gap for            Transmission and if sr-ProhibitTimer is not running:            -   if SR_COUNTER<dsr-TransMax:                -   increment SR_COUNTER by 1;                -   instruct the physical layer to signal the SR on one                    valid PUCCH resource for SR;                -   start the sr-ProhibitTimer.            -   else:                -   notify RRC to release PUCCH for all serving cells;                -   notify RRC to release SRS for all serving cells;                -   clear any configured downlink assignments and uplink                    grants;                -   initiate a Random Access procedure (see subclause                    5.1) on the SpCell and cancel all pending SRs.    -   NOTE: The selection of which valid PUCCH resource for SR to        signal SR on when the MAC entity has more than one valid PUCCH        resource for SR in one TTI is left to UE implementation.    -   NOTE: SR_COUNTER is incremented for each SR bundle.        sr-ProhibitTimer is started in the first TTI of an SR bundle.

5.4.5 Buffer Status Reporting

The Buffer Status reporting procedure is used to provide the serving eNBwith information about the amount of data available for transmission inthe UL buffers associated with the MAC entity. RRC controls BSRreporting by configuring the three timers periodicBSR-Timer,retxBSR-Timer and logicalChannelSR-ProhibitTimer and by, for eachlogical channel, optionally signalling logicalChannelGroup whichallocates the logical channel to an LCG [8].For the Buffer Status reporting procedure, the MAC entity shall considerall radio bearers which are not suspended and may consider radio bearerswhich are suspended.For NB-IoT the Long BSR is not supported and all logical channels belongto one LCG. A Buffer Status Report (BSR) shall be triggered if any ofthe following events occur:

-   -   UL data, for a logical channel which belongs to a LCG, becomes        available for transmission in the RLC entity or in the PDCP        entity (the definition of what data shall be considered as        available for transmission is specified in [3] and [4]        respectively) and either the data belongs to a logical channel        with higher priority than the priorities of the logical channels        which belong to any LCG and for which data is already available        for transmission, or there is no data available for transmission        for any of the logical channels which belong to a LCG, in which        case the BSR is referred below to as “Regular BSR”;    -   UL resources are allocated and number of padding bits is equal        to or larger than the size of the Buffer Status Report MAC        control element plus its subheader, in which case the BSR is        referred below to as “Padding BSR”;    -   retxBSR-Timer expires and the MAC entity has data available for        transmission for any of the logical channels which belong to a        LCG, in which case the BSR is referred below to as “Regular        BSR”;    -   periodicBSR-Timer expires, in which case the BSR is referred        below to as “Periodic BSR”.

For Regular BSR:

-   -   if the BSR is triggered due to data becoming available for        transmission for a logical channel for which        logicalChannelSR-ProhibitTimer is configured by upper layers:        -   start or restart the logicalChannelSR-ProhibitTimer;    -   else:        -   if running, stop the logicalChannelSR-ProhibitTimer.

For Regular and Periodic BSR:

-   -   if more than one LCG has data available for transmission in the        TTI where the BSR is transmitted: report Long BSR;    -   else report Short BSR.

For Padding BSR:

-   -   if the number of padding bits is equal to or larger than the        size of the Short BSR plus its subheader but smaller than the        size of the Long BSR plus its subheader:        -   if more than one LCG has data available for transmission in            the TTI where the BSR is transmitted: report Truncated BSR            of the LCG with the highest priority logical channel with            data available for transmission;        -   else report Short BSR.    -   else if the number of padding bits is equal to or larger than        the size of the Long BSR plus its subheader, report Long BSR.

For NB-IoT:

-   -   if rai-Activation is configured, and a buffer size of zero bytes        has been triggered for the BSR, and the UE may have more data to        send or receive in the near future (FFS):        -   cancel any pending BSR.            If the Buffer Status reporting procedure determines that at            least one BSR has been triggered and not cancelled:    -   if the MAC entity has UL resources allocated for new        transmission for this TTI:        -   instruct the Multiplexing and Assembly procedure to generate            the BSR MAC control element(s);        -   start or restart periodicBSR-Timer except when all the            generated BSRs are Truncated BSRs;        -   start or restart retxBSR-Timer.    -   else if a Regular BSR has been triggered and        logicalChannelSR-ProhibitTimer is not running:        -   if an uplink grant is not configured or the Regular BSR was            not triggered due to data becoming available for            transmission for a logical channel for which logical channel            SR masking (logicalChannelSR-Mask) is setup by upper layers:            -   a Scheduling Request shall be triggered.                A MAC PDU shall contain at most one MAC BSR control                element, even when multiple events trigger a BSR by the                time a BSR can be transmitted in which case the Regular                BSR and the Periodic BSR shall have precedence over the                padding BSR.                The MAC entity shall restart retxBSR-Timer upon                indication of a grant for transmission of new data on                any UL-SCH.                All triggered BSRs shall be cancelled in case the UL                grant(s) in this TTI can accommodate all pending data                available for transmission but is not sufficient to                additionally accommodate the BSR MAC control element                plus its subheader. All triggered BSRs shall be                cancelled when a BSR is included in a MAC PDU for                transmission.                The MAC entity shall transmit at most one                Regular/Periodic BSR in a TTI. If the MAC entity is                requested to transmit multiple MAC PDUs in a TTI, it may                include a padding BSR in any of the MAC PDUs which do                not contain a Regular/Periodic BSR.                All BSRs transmitted in a TTI always reflect the buffer                status after all MAC PDUs have been built for this TTI.                Each LCG shall report at the most one buffer status                value per TTI and this value shall be reported in all                BSRs reporting buffer status for this LCG.

NOTE: A Padding BSR is not allowed to cancel a triggeredRegular/Periodic BSR, except for NB-IoT. A Padding BSR is triggered fora specific MAC PDU only and the trigger is cancelled when this MAC PDUhas been built.

[ . . . ]

5.14.1.4 Buffer Status Reporting

The sidelink Buffer Status reporting procedure is used to provide theserving eNB with information about the amount of sidelink data availablefor transmission in the SL buffers associated with the MAC entity. RRCcontrols BSR reporting for the sidelink by configuring the two timersperiodic-BSR-TimerSL and retx-BSR-TimerSL. Each sidelink logical channelbelongs to a ProSe Destination. Each sidelink logical channel isallocated to an LCG depending on the priority of the sidelink logicalchannel and the mapping between LCG ID and priority which is provided byupper layers in logicalChGroupinfoList [8]. LCG is defined per ProSeDestination.A sidelink Buffer Status Report (BSR) shall be triggered if any of thefollowing events occur:

-   -   if the MAC entity has a configured SL-RNTI or a configured        SL-V-RNTI:        -   SL data, for a sidelink logical channel of a ProSe            Destination, becomes available for transmission in the RLC            entity or in the PDCP entity (the definition of what data            shall be considered as available for transmission is            specified in [3] and [4] respectively) and either the data            belongs to a sidelink logical channel with higher priority            than the priorities of the sidelink logical channels which            belong to any LCG belonging to the same ProSe Destination            and for which data is already available for transmission, or            there is currently no data available for transmission for            any of the sidelink logical channels belonging to the same            ProSe Destination, in which case the Sidelink BSR is            referred below to as “Regular Sidelink BSR”;        -   UL resources are allocated and number of padding bits            remaining after a Padding BSR has been triggered is equal to            or larger than the size of the Sidelink BSR MAC control            element containing the buffer status for at least one LCG of            a ProSe Destination plus its subheader, in which case the            Sidelink BSR is referred below to as “Padding Sidelink BSR”;        -   retx-BSR-TimerSL expires and the MAC entity has data            available for transmission for any of the sidelink logical            channels, in which case the Sidelink BSR is referred below            to as “Regular Sidelink BSR”;        -   periodic-BSR-TimerSL expires, in which case the Sidelink BSR            is referred below to as “Periodic Sidelink BSR”;    -   else:        -   An SL-RNTI or an SL-V-RNTI is configured by upper layers and            SL data is available for transmission in the RLC entity or            in the PDCP entity (the definition of what data shall be            considered as available for transmission is specified in [3]            and [4] respectively), in which case the Sidelink BSR is            referred below to as “Regular Sidelink BSR”.

For Regular and Periodic Sidelink BSR:

-   -   if the number of bits in the UL grant is equal to or larger than        the size of a Sidelink BSR containing buffer status for all LCGs        having data available for transmission plus its subheader:        -   report Sidelink BSR containing buffer status for all LCGs            having data available for transmission;    -   else report Truncated Sidelink BSR containing buffer status for        as many LCGs having data available for transmission as possible,        taking the number of bits in the UL grant into consideration.

For Padding Sidelink BSR:

-   -   if the number of padding bits remaining after a Padding BSR has        been triggered is equal to or larger than the size of a Sidelink        BSR containing buffer status for all LCGs having data available        for transmission plus its subheader:        -   report Sidelink BSR containing buffer status for all LCGs            having data available for transmission;    -   else report Truncated Sidelink BSR containing buffer status for        as many LCGs having data available for transmission as possible,        taking the number of bits in the UL grant into consideration.        If the Buffer Status reporting procedure determines that at        least one Sidelink BSR has been triggered and not cancelled:    -   if the MAC entity has UL resources allocated for new        transmission for this TTI and the allocated UL resources can        accommodate a Sidelink BSR MAC control element plus its        subheader as a result of logical channel prioritization:        -   instruct the Multiplexing and Assembly procedure to generate            the Sidelink BSR MAC control element(s);        -   start or restart periodic-BSR-TimerSL except when all the            generated Sidelink BSRs are Truncated Sidelink BSRs;        -   start or restart retx-BSR-TimerSL;    -   else if a Regular Sidelink BSR has been triggered:        -   if an uplink grant is not configured:            -   a Scheduling Request shall be triggered.                A MAC PDU shall contain at most one Sidelink BSR MAC                control element, even when multiple events trigger a                Sidelink BSR by the time a Sidelink BSR can be                transmitted in which case the Regular Sidelink BSR and                the Periodic Sidelink BSR shall have precedence over the                padding Sidelink BSR.                The MAC entity shall restart retx-BSR-TimerSL upon                reception of an SL grant.                All triggered regular Sidelink BSRs shall be cancelled                in case the remaining configured SL grant(s) valid for                this SC Period can accommodate all pending data                available for transmission in sidelink communication or                in case the remaining configured SL grant(s) valid can                accommodate all pending data available for transmission                in V2X sidelink communication. All triggered Sidelink                BSRs shall be cancelled in case the MAC entity has no                data available for transmission for any of the sidelink                logical channels. All triggered Sidelink BSRs shall be                cancelled when a Sidelink BSR (except for Truncated                Sidelink BSR) is included in a MAC PDU for transmission.                All triggered Sidelink BSRs shall be cancelled, and                retx-BSR-TimerSL and periodic-BSR-TimerSL shall be                stopped, when upper layers configure autonomous resource                selection.                The MAC entity shall transmit at most one                Regular/Periodic Sidelink BSR in a TTI. If the MAC                entity is requested to transmit multiple MAC PDUs in a                TTI, it may include a padding Sidelink BSR in any of the                MAC PDUs which do not contain a Regular/Periodic                Sidelink BSR.                All Sidelink BSRs transmitted in a TTI always reflect                the buffer status after all MAC PDUs have been built for                this TTI. Each LCG shall report at the most one buffer                status value per TTI and this value shall be reported in                all Sidelink BSRs reporting buffer status for this LCG.    -   NOTE: A Padding Sidelink BSR is not allowed to cancel a        triggered Regular/Periodic Sidelink BSR. A Padding Sidelink BSR        is triggered for a specific MAC PDU only and the trigger is        cancelled when this MAC PDU has been built.

6.1.3.1 Buffer Status Report MAC Control Elements

Buffer Status Report (BSR) MAC control elements consist of either:

-   -   Short BSR and Truncated BSR format: one LCG ID field and one        corresponding Buffer Size field (FIG. 6.1.3.1-1); or    -   Long BSR format: four Buffer Size fields, corresponding to LCG        IDs #0 through #3 (FIG. 6.1.3.1-2).        The BSR formats are identified by MAC PDU subheaders with LCIDs        as specified in table 6.2.1-2.        The fields LCG ID and Buffer Size are defined as follow:    -   LCG ID: The Logical Channel Group ID field identifies the group        of logical channel(s) which buffer status is being reported. The        length of the field is 2 bits. For NB-IoT, the LCG ID is set to        #0.    -   Buffer Size: The Buffer Size field identifies the total amount        of data available across all logical channels of a logical        channel group after all MAC PDUs for the TTI have been built.        The amount of data is indicated in number of bytes. It shall        include all data that is available for transmission in the RLC        layer and in the PDCP layer; the definition of what data shall        be considered as available for transmission is specified in [3]        and [4] respectively. The size of the RLC and MAC headers are        not considered in the buffer size computation. The length of        this field is 6 bits. If extendedBSR-Sizes is not configured,        the values taken by the Buffer Size field are shown in Table        6.1.3.1-1. If extendedBSR-Sizes is configured, the values taken        by the Buffer Size field are shown in Table 6.1.3.1-2.    -   [FIG. 6.1.3.1-1 of 3GPP TS 36.321 V14.2.0, entitled “Short BSR        and Truncated BSR MAC control element”, is reproduced as FIG. 5]    -   [FIG. 6.1.3.1-2 of 3GPP TS 36.321 V14.2.0, entitled “Long BSR        MAC control element”, is reproduced as FIG. 6]    -   [Table 6.1.3.1-1 of 3GPP TS 36.321 V14.2.0, entitled “Buffer        size levels for BSR”, is reproduced as FIG. 7]    -   [Table 6.1.3.1-2 of 3GPP TS 36.321 V14.2.0, entitled “Extended        Buffer size levels for BSR”, is reproduced as FIG. 8]

6.1.3.1a Sidelink BSR MAC Control Elements

Sidelink BSR and Truncated Sidelink BSR MAC control elements consist ofone Destination Index field, one LCG ID field and one correspondingBuffer Size field per reported target group.The Sidelink BSR MAC control elements are identified by MAC PDUsubheaders with LCIDs as specified in table 6.2.1-2. They have variablesizes.For each included group, the fields are defined as follows (FIGS.6.1.3.1a-1 and 6.1.3.1a-2):

-   -   Destination Index: The Destination Index field identifies the        ProSe Destination or the destination for V2X sidelink        communication. The length of this field is 4 bits. The value is        set to the index of the destination reported in        destinationInfoList or v2x-DestinationInfoList and if multiple        such lists are reported, the value is indexed sequentially        across all the lists in the same order as specified in [8];    -   LCG ID: The Logical Channel Group ID field identifies the group        of logical channel(s) which buffer status is being reported. The        length of the field is 2 bits;    -   Buffer Size: The Buffer Size field identifies the total amount        of data available across all logical channels of a LCG of a        ProSe Destination after all MAC PDUs for the TTI have been        built. The amount of data is indicated in number of bytes. It        shall include all data that is available for transmission in the        RLC layer and in the PDCP layer; the definition of what data        shall be considered as available for transmission is specified        in [3] and [4] respectively. The size of the RLC and MAC headers        are not considered in the buffer size computation. The length of        this field is 6 bits. The values taken by the Buffer Size field        are shown in Table 6.1.3.1-1;    -   R: Reserved bit, set to “0”.        Buffer Sizes of LCGs are included in decreasing order of the        highest priority of the sidelink logical channel belonging to        the LCG irrespective of the value of the Destination Index        field.    -   [FIG. 6.1.3.1a-1 of 3GPP TS 36.321 V14.2.0, entitled “Sidelink        BSR and Truncated Sidelink BSR MAC control element for even N”,        is reproduced as FIG. 9]    -   [FIG. 6.1.3.1a-2 of 3GPP TS 36.321 V14.2.0, entitled “Sidelink        BSR and Truncated Sidelink BSR MAC control element for odd N”,        is reproduced as FIG. 10]

Logical channel prioritization (LCP) procedure and multiplexing of MACcontrol element and MAC SDUs are described in 3GPP TS 36.321 as follows:

5.4.3 Multiplexing and Assembly 5.4.3.1 Logical Channel Prioritization

The Logical Channel Prioritization procedure is applied when a newtransmission is performed.RRC controls the scheduling of uplink data by signalling for eachlogical channel: priority where an increasing priority value indicates alower priority level, prioritisedBitRate which sets the Prioritized BitRate (PBR), bucketSizeDuration which sets the Bucket Size Duration(BSD). For NB-IoT, prioritisedBitRate, bucketSizeDuration and thecorresponding steps of the Logical Channel Prioritisation procedure(i.e., Step 1 and Step 2 below) are not applicable.The MAC entity shall maintain a variable Bj for each logical channel j.Bj shall be initialized to zero when the related logical channel isestablished, and incremented by the product PBR×TTI duration for eachTTI, where PBR is Prioritized Bit Rate of logical channel j. However,the value of Bj can never exceed the bucket size and if the value of Bjis larger than the bucket size of logical channel j, it shall be set tothe bucket size. The bucket size of a logical channel is equal toPBR×BSD, where PBR and BSD are configured by upper layers.The MAC entity shall perform the following Logical ChannelPrioritization procedure when a new transmission is performed:

-   -   The MAC entity shall allocate resources to the logical channels        in the following steps:        -   Step 1: All the logical channels with Bj>0 are allocated            resources in a decreasing priority order. If the PBR of a            logical channel is set to “infinity”, the MAC entity shall            allocate resources for all the data that is available for            transmission on the logical channel before meeting the PBR            of the lower priority logical channel(s);        -   Step 2: the MAC entity shall decrement Bj by the total size            of MAC SDUs served to logical channel j in Step 1;    -   NOTE: The value of Bj can be negative.        -   Step 3: if any resources remain, all the logical channels            are served in a strict decreasing priority order (regardless            of the value of Bj) until either the data for that logical            channel or the UL grant is exhausted, whichever comes first.            Logical channels configured with equal priority should be            served equally.    -   The UE shall also follow the rules below during the scheduling        procedures above:        -   the UE should not segment an RLC SDU (or partially            transmitted SDU or retransmitted RLC PDU) if the whole SDU            (or partially transmitted SDU or retransmitted RLC PDU) fits            into the remaining resources of the associated MAC entity;        -   if the UE segments an RLC SDU from the logical channel, it            shall maximize the size of the segment to fill the grant of            the associated MAC entity as much as possible;        -   the UE should maximise the transmission of data.        -   if the MAC entity is given an UL grant size that is equal to            or larger than 4 bytes while having data available for            transmission, the MAC entity shall not transmit only padding            BSR and/or padding (unless the UL grant size is less than 7            bytes and an AMD PDU segment needs to be transmitted);        -   for transmissions on serving cells operating according to            Frame Structure Type 3, the MAC entity shall only consider            logical channels for which laa-Allowed has been configured.            The MAC entity shall not transmit data for a logical channel            corresponding to a radio bearer that is suspended (the            conditions for when a radio bearer is considered suspended            are defined in [8]).            If the MAC PDU includes only the MAC CE for padding BSR or            periodic BSR with zero MAC SDUs and there is no aperiodic            CSI requested for this TTI [2], the MAC entity shall not            generate a MAC PDU for the HARQ entity in the following            cases:    -   in case the MAC entity is configured with skip UplinkTxDynamic        and the grant indicated to the HARQ entity was addressed to a        C-RNTI; or    -   in case the MAC entity is configured with skipUplinkTxSPS and        the grant indicated to the HARQ entity is a configured uplink        grant;        For the Logical Channel Prioritization procedure, the MAC entity        shall take into account the following relative priority in        decreasing order:    -   MAC control element for C-RNTI or data from UL-CCCH;    -   MAC control element for SPS confirmation;    -   MAC control element for BSR, with exception of BSR included for        padding;    -   MAC control element for PHR, Extended PHR, or Dual Connectivity        PHR;    -   MAC control element for Sidelink BSR, with exception of Sidelink        BSR included for padding;    -   data from any Logical Channel, except data from UL-CCCH;    -   MAC control element for BSR included for padding;    -   MAC control element for Sidelink BSR included for padding.        -   NOTE: When the MAC entity is requested to transmit multiple            MAC PDUs in one TTI, steps 1 to 3 and the associated rules            may be applied either to each grant independently or to the            sum of the capacities of the grants. Also the order in which            the grants are processed is left up to UE implementation. It            is up to the UE implementation to decide in which MAC PDU a            MAC control element is included when MAC entity is requested            to transmit multiple MAC PDUs in one TTI. When the UE is            requested to generate MAC PDU(s) in two MAC entities in one            TTI, it is up to UE implementation in which order the grants            are processed.

5.4.3.2 Multiplexing of MAC Control Elements and MAC SDUs

The MAC entity shall multiplex MAC control elements and MAC SDUs in aMAC PDU according to subclauses 5.4.3.1 and 6.1.2.

Configuration of logical channel controlled by RRC is described in 3GPPTS 36.331 as follows:

LogicalChannelConfig

The IE LogicalChannelConfig is used to configure the logical channelparameters.

LogicalChannelConfig information element -- ASN1STARTLogicalChannelConfig ::= SEQUENCE {  ul-SpecificParameters  SEQUENCE {  priority     INTEGER (1..16),   prioritisedBitRate  ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, infinity,kBps512-v1020, kBps1024-v1020, kBps2048-v1020, spare5, spare4, spare3,spare2, spare1},   bucketSizeDuration     ENUMERATED {         ms50,ms100, ms150, ms300, ms500, ms1000, spare2,         spare1},  logicalChannelGroup   INTEGER (0..3)     OPTIONAL             -- NeedOR  }   OPTIONAL,                                        -- Cond UL ...,  [[  logicalChannelSR-Mask-r9 ENUMERATED {setup}   OPTIONAL    --Cond SRmask  ]], [[ logicalChannelSR-Prohibit-r12  BOOLEAN  OPTIONAL   -- Need ON  ]], [[ laa-Allowed-r14          BOOLEAN    OPTIONAL    -- Need ON  ]] } --ASN1STOP

LogicalChannelConfig field descriptions bucketSizeDuration Bucket SizeDuration for logical channel prioritization in TS 36.321 [6]. Value inmilliseconds. Value ms50 corresponds to 50 ms, ms100 corresponds to 100ms and so on. laa-Allowed Indicates whether the data of a logicalchannel is allowed to be transmitted via UL of LAA SCells. Value TRUEindicates that the logical channel is allowed to be sent via UL of LAASCells. Value FALSE indicates that the logical channel is not allowed tobe sent via UL of LAA SCells. logicalChannelGroup Mapping of logicalchannel to logical channel group for BSR reporting in TS 36.321 [6].logicalChannelSR-Mask Controlling SR triggering on a logical channelbasis when an uplink grant is configured. See TS 36.321 [6].logicalChannelSR-Prohibit Value TRUE indicates that thelogicalChannelSR-ProhibitTimer is enabled for the logical channel.E-UTRAN only (optionally) configures the field (i.e. indicates valueTRUE) if logicalChannelSR-ProhibitTimer is configured. See TS 36.321[6]. prioritisedBitRate Prioritized Bit Rate for logical channelprioritization in TS 36.321 [6]. Value in kilobytes/second. Value kBps0corresponds to 0 kB/second, kBps8 corresponds to 8 kB/second, kBps16corresponds to 16 kB/second and so on. Infinity is the only applicablevalue for SRB1 and SRB2 priority Logical channel priority in TS 36.321[6]. Value is an integer. Conditional presence Explanation SRmask Thefield is optionally present if ul-SpecificParameters is present, needOR; otherwise it is not present. UL The field is mandatory present forUL logical channels; otherwise it is not present.

The SR and BSR related RRC configurations are described in 3GPP TS36.331 as follows:

MAC-MainConfig

The IE MAC-MainConfig is used to specify the MAC main configuration forsignalling and data radio bearers. All MAC main configuration parameterscan be configured independently per Cell Group (i.e. MCG or SCG), unlessexplicitly specified otherwise.

MAC-MainConfig information element -- ASN1START MAC-MainConfig::=       SEQUENCE {  ul-SCH-Config           SEQUENCE {  maxHARQ-Tx               ENUMERATED {                           n1,n2, n3, n4, n5, n6, n7, n8,                           n10, n12, n16,n20, n24, n28,                           spare2,spare1}    OPTIONAL,  -- Need ON  periodicBSR-Timer          PeriodicBSR-Timer-r12  OPTIONAL,  -- NeedON   retxBSR-Timer            RetxBSR-Timer-r12,  ttiBundling              BOOLEAN }                              OPTIONAL,  -- Need ON drx-Config             DRX-Config      OPTIONAL,  -- Need ON timeAlignmentTimerDedicated     TimeAlignmentTimer, phr-Config             CHOICE {   release                  NULL,  setup                 SEQUENCE {    periodicPHR-Timer            ENUMERATED {sf10, sf20, sf50, sf100, sf200,                               sf500, sf1000, infinity},   prohibitPHR-Timer             ENUMERATED {sf0, sf10, sf20, sf50,sf100,                                    sf200, sf500, sf1000},   dl-PathlossChange             ENUMERATED {dB1, dB3, dB6, infinity}  }  }                                 OPTIONAL,  -- Need ON  ..., [[ sr-ProhibitTimer-r9        INTEGER (0..7)    OPTIONAL   -- Need ON ]],  [[ mac-MainConfig-v1020      SEQUENCE {     sCellDeactivationTimer-r10  ENUMERATED{                          rf2, rf4, rf8, rf16, rf32, rf64, rf128,                          spare}       OPTIONAL,  -- Need OP     extendedBSR-Sizes-r10     ENUMERATED{setup}      OPTIONAL,  -- NeedOR      extendedPHR-r10         ENUMERATED {setup}      OPTIONAL  --Need OR   }                                 OPTIONAL  -- Need ON  ]], [[  stag-ToReleaseList-r11      STAG-ToReleaseList-r11 OPTIONAL,  --Need ON   stag-ToAddModList-r11       STAG-ToAddModList-r11 OPTIONAL,  -- NeedON    drx-Config-v1130          DRX-Config-v1130    OPTIONAL  -- Need ON ]],  [[  e-HARQ-Pattern-r12         BOOLEAN          OPTIONAL,  -- NeedON    dualConnectivityPHR         CHOICE{     release                  NULL,      setup                SEQUENCE{       phr-ModeOtherCG-r12         ENUMERATED{real, virtual}      }   }                               OPTIONAL,  -- Need ON   logicalChannelSR-Config-r12   CHOICE{     release                  NULL,      setup                SEQUENCE {      logicalChannelSR-ProhibitTimer-r12   ENUMERATED {sf20, sf40, sf64,sf128, sf512, sf1024, sf2560, spare1}    }  }                                 OPTIONAL  -- Need ON  ]], [[ drx-Config-v1310         DRX-Config-v1310   OPTIONAL,  -- Need ON   extendedPHR2-r13        BOOLEAN  OPTIONAL,  -- Need ON   eDRX-Config-CycleStartOffset-r13 CHOICE {    release                NULL,     setup                        CHOICE{     sf5120                   INTEGER(0..1),    sf10240                   INTEGER(0..3)     }   }                    OPTIONAL  -- Need ON  ]], [[ drx-Config-r13          CHOICE {     release               NULL,    setup            DRX-Config-r13}                                   OPTIONAL  -- Need ON  ]], [[ skipUplinkTx-r14         CHOICE {     release                NULL,    setup              SEQUENCE {        skipUplinkTxSPS-r14       ENUMERATED {true}    OPTIONAL,  --Need OR         skipUplinkTxDynamie-r14     ENUMERATED{true}    OPTIONAL   -- Need OR      }   }                               OPTIONAL  -- Need ON  ]], [[ dataInactivityTimerConfig-r14   CHOICE {    release                NULL,     setup              SEQUENCE {        dataInactivityTimer-r14      DataInactivityTimer-r14      }    }                        OPTIONAL  -- Need ON  ]] }MAC-MainConfigSCell-r11 ::=     SEQUENCE { stag-Id-r11               STAG-Id-r11 OPTIONAL,  -- Need OP  ... }DRX-Config ::=            CHOICE {  release                   NULL, setup                 SEQUENCE {   onDurationTimer             ENUMERATED {                            psf1, psf2, psf3, psf4, psf5, psf6,                            psf8, psf10, psf20, psf30, psf40,                            psf50, psf60, psf80, psf100,                            psf200},   drx-InactivityTimer            ENUMERATED {                            psf1, psf2, psf3, psf4, psf5, psf6,                            psf8, psf10, psf20, psf30, psf40,                            psf50, psf60, psf80, psf100,                            psf200, psf300, psf500, psf750,                            psf1280, psf1920, psf2560, psf0-v1020,                            spare9, spare8, spare7, spare6,                            spare5, spare4, spare3, spare2,                            spare1},   drx-RetransmissionTimer          ENUMERATED {                            psf1, psf2, psf4, psf6, psf8, psf16,                            psf24, psf33},   longDRX-CycleStartOffset    CHOICE {     sf10                 INTEGER(0..9),     sf20                  INTEGER(0..19),    sf32                  INTEGER(0..31),     sf40                 INTEGER(0..39),     sf64                  INTEGER(0..63),    sf80                  INTEGER(0..79),    sf128                 INTEGER(0..127),    sf160                 INTEGER(0..159),    sf256                 INTEGER(0..255),    sf320                 INTEGER(0..319),    sf512                 INTEGER(0..511),    sf640                 INTEGER(0..639),    sf1024                   INTEGER(0..1023),    sf1280                   INTEGER(0..1279),    sf2048                   INTEGER(0..2047),    sf2560                   INTEGER(0..2559)  }, shortDRX                     SEQUENCE {   shortDRX-Cycle                    ENUMERATED {                                  sf2, sf5, sf8, sf10, sf16, sf20,                                  sf32, sf40, sf64, sf80, sf128, sf160,                                  sf256, sf320, sf512, sf640},   drxShortCycleTimer                   INTEGER (1..16)  }    OPTIONAL                                      -- Need OR  } }DRX-Config-v1130 ::=             SEQUENCE {  drx-RetransmissionTimer-v1130         ENUMERATED{psf0-v1130} OPTIONAL,  -- Need OR  longDRX-CycleStartOffset-v1130         CHOICE {     sf60-v1130                    INTEGER(0..59),     sf70-v1130                    INTEGER(0..69) }                                        OPTIONAL,  -- Need OR shortDRX-Cycle-v1130                ENUMERATED {sf4-v1130} OPTIONAL  --Need OR } DRX-Config-v1310 ::=              SEQUENCE { longDRX-CycleStartOffset-v1310        SEQUENCE {  sf60-v1310                       INTEGER(0..59) }                                        OPTIONAL   -- Need OR }DRX-Config-r13 ::=               SEQUENCE {  onDurationTimer-v1310                ENUMERATED {psf300, psf400,psf500, psf600,                                    psf800, psf1000,psf1200, psf1600}                               OPTIONAL,  -- Need OR  drx-RetransmissionTimer-v1310          ENUMERATED {psf40, psf64,psf80, psf96, psf112,                                    psf128, psf160,psf320}                                       OPTIONAL,  -- Need OR  drx-ULRetransmissionTimer-r13          ENUMERATED {psf0, psf1, psf2,psf4, psf6, psf8, psf16,                                      psf24,psf33, psf40, psf64, psf80, psf96,                                     psf112, psf128, psf160, psf320}                                     OPTIONAL  -- Need OR }PeriodicBSR-Timer-r12 ::=              ENUMERATED {                                sf5, sf10, sf16, sf20, sf32, sf40, sf64,sf80,                                 sf128, sf160, sf320, sf640,sf1280, sf2560,                                 infinity, spare1 }RetxBSR-Timer-r12 ::=                  ENUMERATED {                                sf320, sf640, sf1280, sf2560, sf5120,                                sf10240, spare2, spare1 }STAG-ToReleaseList-r11::= SEQUENCE (SIZE (1..maxSTAG-r11)) OFSTAG-Id-r11 STAG-ToAddModList-r11::=  SEQUENCE (SIZE (1..maxSTAG-r11))OF STAG-ToAddMod-r11 STAG-ToAddMod-r11::=    SEQUENCE {  stag-Id-r11           STAG-Id-r11,  timeAlignmentTimerSTAG-r11   TimeAlignmentTimer,   ... }STAG-Id-r11::=        INTEGER (1..maxSTAG-r11) -- ASN1STOP

MAC-MainConfig field descriptions dl-PathlossChange DL Pathloss Changeand the change of the required power backoff due to power management (asallowed by P-MPRc [42]) for PHR reporting in TS 36.321 [6]. Value in dB.Value dB1 corresponds to 1 dB, dB3 corresponds to 3 dB and so on. Thesame value applies for each serving cell (although the associatedfunctionality is performed independently for each cell). drx-Config Usedto configure DRX as specified in TS 36.321 [6]. E-UTRAN configures thevalues in DRX- Config-v1130 only if the UE indicates support for IDCindication. E-UTRAN configures drx- Config-v1130, drx-Config-v1310 anddrx-Config-r13 only if drx-Config (without suffix) is configured.E-UTRAN configures drx-Config-r13 only if UE supports CE or if the UE isconfigured with uplink of an LAA SCell. drx-InactivityTimer Timer forDRX in TS 36.321 [6]. Value in number of PDCCH sub-frames. Value psf0corresponds to 0 PDCCH sub-frame and behaviour as specified in 7.3.2applies, value psf1 corresponds to 1 PDCCH sub-frame, psf2 correspondsto 2 PDCCH sub-frames and so on. drx-Retransmission Timer Timer for DRXin TS 36.321 [6]. Value in number of PDCCH sub-frames. Value psf0corresponds to 0 PDCCH sub-frame and behaviour as specified in 7.3.2applies, value psf1 corresponds to 1 PDCCH sub-frame, psf2 correspondsto 2 PDCCH sub-frames and so on. In case drx-RetransmissionTimer-v1130or drx-RetransmissionTimer-v1310 is signalled, the UE shall ignoredrx-RetransmissionTimer (i.e. without suffix). drx-ULRetransmissionTimerTimer for DRX in TS 36.321 [6]. Value in number of PDCCH sub-frames.Value psf0 correponds to 0 PDCCH sub-frame and behaviour as specified in7.3.2 applies, value psf1 corresponds to 1 PDCCH sub-frame, psf2corresponds to 2 PDCCH sub-frames and so on. drxShortCycleTimer Timerfor DRX in TS 36.321 [6]. Value in multiples of shortDRX-Cycle. A valueof 1 corresponds to shortDRX-Cycle, a value of 2 corresponds to 2 *shortDRX-Cycle and so on. dualConnectivityPHR Indicates if powerheadroom shall be reported using Dual Connectivity Power Headroom ReportMAC Control Element defined in TS 36.321 [6] (value setup). If PHRfunctionality and dual connectivity are configured, E-UTRAN alwaysconfigures the value setup for this field and configures phr-Config anddualConnectivityPHR for both CGs. e-HARQ-Pattern TRUE indicates thatenhanced HARQ pattern for TTI bundling is enabled for FDD. E-UTRANenables this field only when ttiBundling is set to TRUE.eDRX-Config-CycleStartOffset Indicates longDRX-Cycle and drxStartOffsetin TS 36.321 [6]. The value of longDRX-Cycle is in number of sub-frames.The value of drxStartOffset, in number of subframes, is indicated by thevalue of eDRX-Config-CycleStartOffset multiplied by 2560 plus the offsetvalue configured in longDRX-CycleStartOffset. E-UTRAN only configuresvalue setup when the value in longDRX- CycleStartOffset is sf2560.extendedBSR-Sizes If value setup is configured, the BSR index indicatesextended BSR size levels as defined in TS 36.321 [6, Table 6.1.3.1-2].extendedPHR Indicates if power headroom shall be reported using theExtended Power Headroom Report MAC control element defined in TS 36.321[6] (value setup). E-UTRAN always configures the value setup if morethan one and up to eight Serving Cell(s) with uplink is configured andnone of the serving cells with uplink configured has a servingCellIndexhigher than seven and if PUCCH on SCell is not configured and if dualconnectivity is not configured. E-UTRAN configures extendedPHR only ifphr-Config is configured. The UE shall release extendedPHR if phr-Configis released. extendedPHR2 Indicates if power headroom shall be reportedusing the Extended Power Headeroom Report MAC Control Element defined inTS 36.321 [6] (value setup). E-UTRAN always configures the value setupif any of the serving cells with uplink configured has aservingCellIndex higher than seven in case dual connectivity is notconfigured or if PUCCH SCell (with any number of serving cells withuplink configured) is configured. E-UTRAN configures extendedPHR2 onlyif phr- Config is configured. The UE shall release extendedPHR2 ifphr-Config is released. logicalChannelSR-ProhibitTimer Timer used todelay the transmission of an SR for logical channels enabled bylogicalChannelSR- Prohibit. Value sf20 corresponds to 20 subframes, sf40corresponds to 40 subframes, and so on. See TS 36.321 [6].longDRX-CycleStartOffset longDRX-Cycle and drxStartOffset in TS 36.321[6] unless eDRX-Config-CycleStartOffset is configured. The value oflongDRX-Cycle is in number of sub-frames. Value sf10 corresponds to 10sub-frames, sf20 corresponds to 20 sub-frames and so on. IfshortDRX-Cycle is configured, the value of longDRX-Cycle shall be amultiple of the shortDRX-Cycle value. The value of drxStartOffset valueis in number of sub-frames. In case longDRX-CycleStartOffset-v1130 issignalled, the UE shall ignore longDRX-CycleStartOffset (i.e. withoutsuffix). In case longDRX- CycleStartOffset-v1310 is signalled, the UEshall ignore longDRX-CycleStartOffset (i.e. without suffix). maxHARQ-TxMaximum number of transmissions for UL HARQ in TS 36.321 [6]. onDurationTimer Timer for DRX in TS 36.321 [6]. Value in number of PDCCHsub-frames. Value psf1 corresponds to 1 PDCCH sub-frame, psf2corresponds to 2 PDCCH sub-frames and so on. In caseonDurationTimer-v1310 is signalled, the UE shall ignore onDurationTimer(i.e. without suffix). periodicBSR-Timer Timer for BSR reporting in TS36.321 [6]. Value in number of sub-frames. Value sf10 corresponds to 10sub-frames, sf20 corresponds to 20 sub-frames and so on.periodicPHR-Timer Timer for PHR reporting in TS 36.321 [6]. Value innumber of sub-frames. Value sf10 corresponds to 10 subframes, sf20corresponds to 20 subframes and so on. phr-ModeOtherCG Indicates themode (i.e. real or virtual) used for the PHR of the activated cells thatare part of the other Cell Group (i.e. MCG or SCG), when DC isconfigured. prohibitPHR-Timer Timer for PHR reporting in TS 36.321 [6].Value in number of sub-frames. Value sf0 corresponds to 0 subframes andbehaviour as specified in 7.3.2 applies, sf100 corresponds to 100subframes and so on. retxBSR-Timer Timer for BSR reporting in TS 36.321[6]. Value in number of sub-frames. Value sf640 corresponds to 640sub-frames, sf1280 corresponds to 1280 sub-frames and so on.sCellDeactivationTimer SCell deactivation timer in TS 36.321 [6]. Valuein number of radio frames. Value rf4 corresponds to 4 radio frames,value rf8 corresponds to 8 radio frames and so on. E-UTRAN onlyconfigures the field if the UE is configured with one or more SCellsother than the PSCell and PUCCH SCell. If the field is absent, the UEshall delete any existing value for this field and assume the value tobe set to infinity. The same value applies for each SCell of a CellGroup (i.e. MCG or SCG) (although the associated functionality isperformed independently for each SCell). Field sCellDeactivationTimerdoes not apply for the PUCCH SCell. shortDRX-Cycle Short DRX cycle in TS36.321 [6]. Value in number of sub-frames. Value sf2 corresponds to 2sub-frames, sf5 corresponds to 5 subframes and so on. In caseshortDRX-Cycle-v1130 is signalled, the UE shall ignore shortDRX-Cycle(i.e. without suffix). Short DRX cycle is not configured for UEs in CE.skipUplinkTxDynamic If configured, the UE skips UL transmissions for anuplink grant other than a configured uplink grant if no data isavailable for transmission in the UE buffer as described in TS 36.321[6]. skip UplinkTxSPS If configured, the UE skips UL transmissions for aconfigured uplink grant if no data is available for transmission in theUE buffer as described in TS 36.321 [6]. E-UTRAN always configuresskipUplinkTxSPS when semiPersistSchedIntervalUL is shorter than sf10.sr-ProhibitTimer Timer for SR transmission on PUCCH in TS 36.321 [6].Value in number of SR period(s) of shortest SR period of any servingcell with PUCCH. Value 0 means that behaviour as specified in 7.3.2applies. Value 1 corresponds to one SR period, Value 2 corresponds to2*SR periods and so on. SR period is defined in TS 36.213 [23, table10.1.5-1]. stag-Id Indicates the TAG of an SCell, see TS 36.321 [6].Uniquely identifies the TAG within the scope of a Cell Group (i.e. MCGor SCG). If the field is not configured for an SCell (e.g. absent inMAC-MainConfigSCell), the SCell is part of the PTAG. stag-ToAddModList,stag-ToReleaseList Used to configure one or more STAGs. E-UTRAN ensuresthat a STAG contains at least one SCell with configured uplink. If, dueto SCell release a reconfiguration would result in an ‘empty’ TAG,E-UTRAN includes release of the concerned TAG. timeAlignmentTimerSTAGIndicates the value of the time alignment timer for an STAG, see TS36.321 [6]. ttiBundling TRUE indicates that TTI bundling TS 36.321 [6]is enabled while FALSE inidcates that TTI bundling is disabled. TTIbundling can be enabled for FDD and for TDD only for configurations 0, 1and 6. The functionality is performed independently per Cell Group (i.e.MCG or SCG), but E-UTRAN does not configure TTI bundling for the SCG.For a TDD PCell, E-UTRAN does not simultaneously enable TTI bundling andsemi-persistent scheduling in this release of specification.Furthermore, for a Cell Group, E-UTRAN does not simultaneously configureTTI bundling and SCells with configured uplink, and E-UTRAN does notsimultaneously configure TTI bundling and eIMTA.

The progress of RAN2 in study item for NR design is captured in 3GPP TS38.804. 3GPP TS 38.804 specifies that multiple numerologies aresupported and logical channel in NR could be associated with TTIdurations and/or numerologies. The main purpose of such association isfor achieving service requirement. For example, urgent services could beassociated with shorter TTIs for latency reduction. In the meantime,shorter TTIs also provide more opportunities for data transmissions toachieve higher data rate. Definitions of numerology and TTI duration aredescribed in 3GPP TS 38.804 as follows:

5.4.7 Numerologies and TTI Durations

One numerology corresponds to one subcarrier spacing in the frequencydomain. By scaling a basic subcarrier spacing by an integer N, differentnumerologies can be defined in TR 38.802 [14].One TTI duration corresponds to a number of consecutive symbols in thetime domain in one transmission direction. Different TTI durations canbe defined when using different number of symbols (e.g. corresponding toa mini-slot, one slot or several slots in one transmission direction).The combination of one numerology and one TTI duration determines howtransmission is to be made on the physical layer.Which numerologies and/or TTI durations a logical channel of a radiobearer is mapped to can be configured and reconfigured via RRCsignalling. The mapping is not visible to RLC, i.e. the RLCconfiguration is per logical channel with no dependency on numerologiesand/or TTI durations, and ARQ can operate on any of the numerologiesand/or TTI durations the logical channel is configured with.A single MAC entity can support one or multiple numerologies and/or TTIdurations but in order for the mapping to be respected, logical channelprioritization procedure takes into account the mapping of one LCH toone or more numerologies and/or TTI durations.

-   -   NOTE: HARQ operation with multiple numerologies and TTI        durations is FFS, and it should be discussed and decided by        RAN1.    -   NOTE: Whether any characteristic of the numerology beyond the        TTI is visible to MAC is FFS (depending on progress in RAN1).

In RAN2 #97bis meeting, a new agreement related to SR design was made asfollows:

Agreements on SR/BSR

-   -   The SR should at least distinguish the “numerology/TTI type” of        the logical channel that triggered the SR (how this is done is        FFS).

In RAN2 #98 meeting, new agreements related to SR design were made asfollows:

Agreements

1. Multiple SR configurations can be configured to the UE and which SRconfiguration is used depends on the LCH that triggers the SR. Thegranularity of SR configuration for a logical channel is FFS.2. From RAN2 point of view a single bit SR with multiple SRconfiguration is sufficient to distinguish the “numerology/TTI length”of the logical channel that trigger the SR. RAN2 has not identifiedother use cases for which multibit SR is need with sufficient support.3. RAN2 does not see the need to convey buffer status information.4. Send LS to RAN1 to indicate to RAN1 that RAN2 doesn't see the need tosupport multi-bit SR.

Based on the latest agreement, a SR will need to reflect TTI and/ornumerology information of the uplink logical channel which triggers theSR. The main purpose of such agreement is to accelerate uplink resourcerequest and to avoid resource waste caused by TTI/numerologyconfiguration of logical channels. How to reflect TTI and/or numerologyinformation will need further study. Potential methods are discussedbelow.

Method 1—Network provides multiple SR configurations to UE. Different SRconfigurations may contain different radio resources in frequencydomain, time domain, and/or code domain and each SR configuration islinked to TTI/numerology information. The linking could be establishedbased on implicit association (e.g., a numerology used for SRtransmission according to a SR configuration is linked to requesting theresource on the numerology) and/or explicit association (e.g.,TTI/numerology information is included in each SR configuration). TheTTI/numerology information could be one or multiple followingcandidates:

-   1. Numerology (e.g. numerology index)-   2. TTI length/duration (e.g. maximum TTI threshold, specific TTI    length/duration (range))-   3. Logical channel identity-   4. Logical channel group identity-   5. Logical channel priority-   6. QoS flow ID

And the UE may directly associate SR configuration with logicalchannel(s) explicitly or implicitly. For example, if SR configurationincludes logical channel (group) identity, the data belonging to certainlogical channel (group) arrives may trigger BSR and may also triggercorresponding SR based on SR configuration. As another example, if eachSR configuration includes numerology information for performing SRtransmission, data belonging to certain logical channel (group) arrives,then a SR configuration using same numerology as the logical channel(group) suggested to use will be triggered.

Method 2—A new SR with multiple bits is defined in NR. The multiple bitsin SR could be designed as one or multiple fields. Each field could beused to indicate one or multiple information listed as follows:

-   1. Numerology-   2. TTI length/duration (e.g. maximum TTI threshold, specific TTI    length/duration (range))-   3. Logical channel identity (e.g. bitmaps representing different    logical channels, field for indicating LCID)-   4. Logical channel group identity-   5. Logical channel priority-   6. QoS flow ID

One possible example could be there are two fields in a SR. The firstfield represents numerology, and the second field represents TTIlength/duration. If a logical channel suggested to numerology A andnumerology B and TTI length below 0.5 ms has data coming, the SR couldindicate numerology A and numerology B in the first field and indicateTTI below 0.5 ms in the second field. Alternatively, the SR couldindicate either numerology A or numerology B in the first field andindicate TTI below 0.5 ms in the second field. Alternatively, the SRcould indicate only numerology A in the first field and indicate TTIbelow 0.5 ms in the second field. The UE that only indicates numerologyA may depend on network configuration (e.g. network configures UE toindicate which one, UE only receives numerology A configuration fromnetwork, . . . ). The UE only indicating numerology A may depend onshorter slot length on numerology A. In one embodiment, the logicalchannel has highest priority comparing with priorities of other logicalchannels with data available for transmission.

Another example could be one field in a SR for indicating logicalchannel identity. A UE will set the LCID to identity of the logicalchannel with highest priority in all logical channels having data. Sincenetwork provides TTI and/or numerology configuration of logical channelto the UE, network can understand the TTI/numerology need of the UE.

Method 3—This method is a hybrid of the previous two methods. MultipleSR configurations could be configured to a UE, and at least one of thoseSR configurations supports multiple bits SR. The multiple SRconfigurations and multiple bits SR independently represent one ormultiple following information:

-   1. Numerology-   2. TTI length/duration (e.g. maximum TTI threshold, specific TTI    length/duration (range))-   3. Logical channel identity (e.g. bitmaps representing different    logical channels, field for indicating LC ID)-   4. Logical channel group identity-   5. Logical channel priority-   6. QoS flow ID

The information represents by multiple bits SR and multiple SRconfigurations could be different or have certain level overlap. Forexample, multiple bits SR are used to indicate specific LCID withincertain group of logical channels, while different SR configurations areused to indicate whether data is available in different group of logicalchannels. The specific LCID could be used to identify logical channelwith highest priority or shortest TTI and/or numerology with the groupof logical channels which having data. As another example, multiple bitsSR and different SR configuration are used to indicate differentinformation. The multiple bits SR is used to indicate TTIlength/duration information and the multiple SR configurations are usedto indicate different numerologies.

On the other hand, there are still some possible cases not covered bythe agreement. It is not clear how to handle SR triggering/setting forthose cases. Those possible cases are observed and listed below.

Case 1: Sidelink BSR

In LTE, sidelink interface is introduced for direct communicationbetween UEs. Similar to BSR, Sidelink BSR is used to request sidelinkresource from base station. A UE will trigger SR when it needs totransmit sidelink BSR and has no uplink resource. Since the base stationwill provide only uplink resource for responding SR from a UE and uplinkresource cannot be used for sidelink transmission, the resource wastemay still occur following the latest agreement. Moreover, it is notclear whether a sidelink logical channel will be associated with the TTIlength and/or numerology.

Case 2: Timer and/or Counter Controlled Based Control Element (e.g.Retx-BSR Timer)

In LTE, there are some timers and/or counters designed for handlingun-expecting conditions. When the counters reach a threshold or thetimers expire, the UE may trigger MAC control element and may furthertrigger SR. Retransmission BSR timer is one example in LTE. Morespecifically, for retransmission BSR timer case, the UE triggers BSR ifthe retransmission timer expires and the UE still has data available fortransmission for any of the logical channels belonging to a LCG. In NR,it is quite possible to use such design in many procedures. If anun-expected MAC control element is triggered by timer and/or counter,the UE may trigger SR for forwarding the MAC control element to networkas soon as possible.

Case 3: Potential New Uplink MAC Control Element which can Trigger SR

New control element(s) could be introduced in NR for different purposes.Here, the new control element(s) will trigger SR. The new controlelement is designed for UE to autonomously report information to thenetwork (e.g. base station, TRP, CU and/or DU, etc.). The new MACcontrol element may or may not be related to logical channel. Forexample, there could be beam related control element (e.g. beam report,beam quality report, beam failure indication, etc.). Since UE may detectsuch condition sooner than network side, the beam related controlelement may need to report to network as soon as possible. The beamrelated control element may be for uplink and/or downlink. The beamrelated control element may be for UE beam and/or network beam.

As another example, SPS assistance information message is introduced inRel-14. There could be a new MAC control element for rapidly updatingthe latest information. The new MAC control element may indicate one ormultiple information listed below for assisting network to updatecorresponding SPS:

-   1. Logical channel identity-   2. SPS configuration index-   3. Cell and/or frequency information-   4. Beam information-   5. Radio bearer identity-   6. QoS flow ID-   7. Periodicity-   8. Start offset-   9. Indication for whether Service/traffic is terminated-   10. Packet size (e.g. TB size, MAC PDU size, RLC PDU size, PDCP PDU    size, IP packet size, etc.)

Since network may not be able to immediately detect traffic patternchange, it is better for the new control element being able to triggerSR when UE has no uplink resource.

The other possible information, which could be reported by the new MACCE, can be one or multiple following information:

-   1. DL Channel quality-   2. Data rate-   3. Data arrival-   4. UE transmission power-   5. Traffic characteristic of one or multiple RBs and/or one or    multiple logical channels change (e.g. message size, latency    requirement, priority, communication path (uplink, sidelink, relay,    etc.), MCS suggestion, reliability, destination and/or source of    sidelink, RNTI association, mapping between RB and QoS flow ID,    transmission power setting, how many (re)transmission opportunities,    mapping between cell and RB/LC, mapping between HARQ process/entity    and LC/RB, etc.)-   6. UE beam-forming (e.g. how many beams in any time, power    limitation after beam-forming, beam-forming on-off, etc.)-   7. UE mode (e.g. coverage enhanced mode, etc.)-   8. UE mobility (e.g. speed, etc.)-   9. Congestion detection (e.g. detecting whether a specific time    sidelink and/or uplink is congested, etc.)

Moreover, the new MAC CE could also be a request for initiating certainservice or function. The service or function could be one or multiplefollowing candidates.

-   1. System information request (e.g. other SI request MAC CE)-   2. Resource request (e.g. (sidelink) contention resource request,    grant-free resource request, preamble resource request, reserved    uplink/sidelink resource in specific timing and/or specific    continuous period, etc.)-   3. Time Alignment request-   4. Packet duplication function request-   5. Cell activation/deactivation request-   6. Downlink MAC CE request-   7. TTI bundling request-   8. Positioning request-   9. HARQ configuration change request (e.g. change HARQ process    number and/or reset HARQ-   10. Change data rate request (e.g. data rate of UE, data rate of    certain cell, and/or data rate of one or multiple LCs, etc.)

Possible cases based on each aforementioned method are discussed below;In one embodiment, logical channel mentioned below belongs to a LCG.Alternatively, logical channel mentioned below doesn't have to belong toa LCG.

Applying Method 1—In case 1, possible options are proposed for handlinghow sidelink BSR trigger SR for requesting uplink resource.

Option 1 (Pre-defined rule for UE to select SR configuration)—Possibly,the UE triggers SR transmission according to SR configuration associatedwith default or access numerology when SR is triggered due to sidelinkBSR. The default numerology could be default numerology defined inspecification for control element to request resource. The defaultnumerology could be numerology used for receiving system information inRRC_IDLE state and/or RRC_INACTIVE state. The default numerology couldbe a numerology used for performing initial access. The defaultnumerology could be different for different UEs (e.g. NB-IoT UE andnormal UE may have different default numerologies due to UE capability).

Another possibility could be that UE always triggers SR transmissionaccording to SR configuration associated with the largest (e.g. SCS=480khz, SCS=120 khz) or the smallest numerology (e.g. SCS=15 khz, SCS=2.5khz) which the UE can use. The numerology which a UE can use will needto take UE capability into account. In one embodiment, the numerologywhich a UE can use will also need to take configuration provided fromnetwork into account. If the UE does not have a configuration related tocertain numerology, the UE may not be able to transmit SR on thatnumerology even the UE is capable to use. The configuration could be SRconfiguration.

Another possibility could be that UE always triggers SR transmissionaccording to SR configuration with the densest SR transmissionopportunity. Yet another possibility could be that UE triggers SRtransmission using all SR configurations the UE being configured.

Moreover, the numerology could be replaced by one or multipleTTI/numerology information (e.g. LCG and/or TTI length, etc.) mentionedin the description of Method 1. Alternatively, considering all possiblesimple rules mentioned above, another possibility could be the networkconfigures which rule a UE shall follow when sidelink BSR is triggered.

Option 2 (Network configures the association between sidelink BSR and SRconfiguration)—Possibly, the network could provide numerology and/or TTIinformation to a service (e.g. sidelink, MBMS, V2X, V2V, relay, MTC,URLLC, IoT etc.). And a MAC control element related to the service willtrigger SR transmission by similar rule as logical channel with data.The MAC control element will trigger SR transmission according to SRconfiguration associated with the numerology and/or TTI information. Thenumerology and/or TTI information could be provided in serviceconfiguration (e.g. sidelink communication configuration, sidelinkdiscovery configuration, etc.).

Another possibility could be that network provides numerology and/or TTIinformation to a MAC control element. The MAC control element willtrigger SR transmission according to SR configuration associated withthe numerology and/or TTI information. Moreover, the MAC control elementmay or may not be limited to only use uplink resource related to thenumerology and/or TTI information for transmission.

Yet another possibility could be that SR configuration includes MACcontrol element information (e.g. LCID(s) of MAC control element(s), MACcontrol element corresponding bitmap, etc.).

Moreover, the numerology and/or TTI information could be replaced by oneor multiple information mentioned in description of Method 1.

Another possibility could be that network provides SR configurationindex/identity in service configuration related to the MAC controlelement. And the UE triggers SR according to the SR configurationindex/identity for the MAC control element.

Option 3 (All SR configurations can be candidates, and the UE selectsone of them)—The UE could possibly trigger SR transmission according tothe SR configuration which has the closest SR transmission opportunityto the MAC control element trigger timing. The closest SR transmissionmay need to take UE processing capability into account.

Option 4 (Defined SR configuration for control element (e.g. SidelinkBSR))—The UE could possibly be configured with a SR configuration usedto dedicatedly handle one or multiple MAC control element(s). Therecould be more than one SR configurations used to dedicated for handlingMAC control elements.

Option 5 (UE can autonomously select one of multiple SR configurations,instead of all SR configurations, and the multiple SR configurations aredecided based on some conditions)—The UE could possibly be configuredwith one or multiple criteria for deciding appropriate set of SRconfigurations. The criteria could be threshold for TTI length and/ornumerology. The criteria could be LCG(s).

Option 6 (UE triggers SR configuration related to logical channel havingdata)—Assuming the sidelink logical channel will also be associateddifferent TTI lengths and/or numerologies, the UE could apply solutionsimilar to uplink design.

The UE could possibly trigger SR transmission according to SRconfiguration associated with TTI length and/or numerology of highestpriority sidelink logical channel within all sidelink logical channelshaving data in all ProSe destinations. Another possibility could be thatthe UE triggers SR transmission according to SR configuration associatedwith TTI length and/or numerology of sidelink logical channel for latestsidelink BSR triggering.

In case 2, the following possible options for handling SR triggering fora timer and/or counter controlled based control element are consideredand proposed:

Option 1 (Pre-defined rule for UE to select SR configuration)—The UEcould possibly trigger SR transmission according to SR configurationassociated with default or access numerology when the control elementneeds to trigger SR. The default numerology could be default numerologydefined in specification for control element to request resource. Thedefault numerology could be numerology used for receiving systeminformation in RRC_IDLE state and/or RRC_INACTIVE state. The defaultnumerology could be a numerology used for performing initial access. Thedefault numerology could be different for different UEs (e.g. NB-IoT UEand normal UE may have different default numerologies due to UEcapability).

Alternatively, the UE could always triggers SR transmission according toSR configuration associated with the largest or the smallest numerologywhich the UE could use. The numerology that a UE could use would need totake UE capability into account. In one embodiment, the numerology thata UE could use would also need to take configuration provided fromnetwork into account. If the UE does not have a configuration related tocertain numerology, the UE may not be able to transmit SR on thatnumerology even the UE is capable to use. The configuration could be SRconfiguration.

Another possibility could be that UE always SR transmission according toSR configuration with the densest SR transmission opportunity. Yetanother possibility could be that UE triggers SR transmission on all SRconfigurations the UE being configured. Moreover, the numerology couldbe replaced by one or multiple TTI/numerology information (e.g. LCGand/or TTI length, . . . ) mentioned in the description of Method 1.Alternatively, considering all possible simple rules mentioned above,another possibility could be network configures which rule a UE shallfollow when timer/counter control based MAC CE is triggered.

Option 2 (Network configures the association between such timer/countercontrol based MAC CE and SR configuration)—The network could possiblyprovide numerology and/or TTI information to a service (e.g. sidelink,MBMS, V2X, V2V, relay, MTC, URLLC, IoT etc.). A MAC control elementrelated to the service will trigger SR configuration by similar rule aslogical channel with data. The MAC control element will trigger SRtransmission according to SR configuration associated with thenumerology and/or TTI information. The numerology and/or TTI informationcould be provided in service configuration (e.g. sidelink communicationconfiguration, sidelink discovery configuration, etc.).

Alternatively, the network could possibly provide numerology and/or TTIinformation to a MAC control element. More specifically, the numerologyand/or TTI information could be provided to specific timer or counterfor handling timer/counter controlled based MAC CE in case 2. The MACcontrol element will trigger SR transmission according to SRconfiguration associated with the numerology and/or TTI information.Moreover, the MAC control element may or may not be limited to only useuplink resource related to the numerology and/or TTI information fortransmission.

Another possibility could be that SR configuration includes MAC controlelement information (e.g. LCID(s) of MAC control element(s), MAC controlelement corresponding bitmap, timer and/or counter IE related totimer/counter control based MAC CE). Moreover, the numerology and/or TTIinformation could be replaced by one or multiple information mentionedin description of Method 1.

Another possibility could be that network provides SR configurationindex/identity in service configuration related to the MAC controlelement. And the UE triggers SR according to the SR configurationindex/identity for the MAC control element.

Option 3 (All SR configurations can be candidate, and UE selects one ofthem)—The UE could possibly trigger SR transmission according to SRconfiguration which has the closest SR transmission opportunity to theMAC control element trigger timing. The closest SR transmission may needto take UE processing capability into account.

Option 4—(Defined SR configuration for control element (e.g. fortimer/counter control based MAC CE, for MAC CE not related to logicalchannel))—The UE would possibly be configured with a SR configurationused to dedicatedly handle one or multiple MAC control element(s). Therecould be more than one SR configurations used to dedicated for handlingMAC control elements.

Option 5—(UE could autonomously select one of multiple SRconfigurations, instead of all SR configurations; and the multiple SRconfigurations are decided based on some conditions)—The UE wouldpossibly be configured with one or multiple criteria for decidingappropriate set of SR configurations. The criteria could be thresholdfor TTI length and/or numerology. The criteria could be LCG(s).

Option 6 (Trigger SR based on buffer status)—The UE possibly trigger SRtransmission based on current which logical channel(s) having data. Morespecifically, the UE would trigger SR transmission according to SRconfiguration associated with the TTI and/or numerology of the highestpriority logical channel within all (sidelink) logical channels havingdata.

Alternatively, the UE could trigger SR transmission according to SRconfiguration associated with LCG of the highest priority logicalchannel within all (sidelink) logical channels having data.

Option 7 (Trigger SR based on timer/counter parameter)—Normally, a timerand/or counter will increase or decrease based on certain time unit.Possibly, a UE triggers SR transmission according to SR configurationassociated with the time unit. There may be parameters (e.g. 1 slot, 14OFDM symbols, etc.) for translate time unit to corresponding numerologyand/or TTI. For example, if 1 ms subframe is the time unit of a timerand UE triggers a control element controlled by the timer, the controlelement will use SR configuration on 15 khz numerology.

In case 3, possible options for handling SR triggering for potential newcontrol element are as follows:

Option 1 (Pre-defined rule for UE to select SR configuration)—The UEpossibly triggers SR transmission according to SR configurationassociated with default or access numerology when new MAC CE needs totrigger SR. The default numerology could be default numerology definedin specification for control element to request resource. The defaultnumerology could be numerology used for receiving system information inRRC_IDLE state and/or RRC_INACTIVE state. The default numerology couldbe a numerology used for performing initial access. The defaultnumerology could be different for different UEs (e.g. NB-IoT UE andnormal UE may have different default numerologies due to UE capability).

Alternatively, the UE could always triggers SR transmission according toSR configuration associated with the largest or the smallest numerologywhich the UE can use. The numerology which a UE can use will need totake UE capability into account. In one embodiment, the numerology thata UE could use would also need to take configuration provided fromnetwork into account. If the UE does not have a configuration related tocertain numerology, the UE may not be able to transmit SR on thatnumerology even the UE is capable to use. The configuration could be SRconfiguration.

Another possibility could be that UE always SR transmission according toSR configuration with the densest SR transmission opportunity. Yetanother possibility could be that UE triggers SR transmission on all SRconfigurations the UE being configured. Moreover, the numerology couldbe replaced by one or multiple TTI/numerology information (e.g. LCGand/or TTI length, . . . ) mentioned in the description of Method 1.Alternatively, considering all possible simple rules mentioned above,another possibility could be network configures which rule a UE shallfollow when the new control element is triggered.

Option 2 (Network configures the association between new MAC CE and SRconfiguration)—Possibly, network could provide numerology and/or TTIinformation to a service (e.g. sidelink, MBMS, V2X, V2V, relay, MTC,URLLC, IoT etc.). And a MAC control element related to the service willSR transmission of a SR configuration by similar rule as logical channelwith data. The MAC control element will trigger SR transmissionaccording to SR configuration associated with the numerology and/or TTIinformation. The numerology and/or TTI information could be provided inservice configuration (e.g. sidelink communication configuration,sidelink discovery configuration, etc.).

Another possibility could be that network provides numerology and/or TTIinformation to a MAC control element. The MAC control element willtrigger SR transmission according to SR configuration associated withthe numerology and/or TTI information. Moreover, the MAC control elementmay or may not be limited to only use uplink resource related to thenumerology and/or TTI information for transmission.

Another possibility could be that SR configuration includes MAC controlelement information (e.g. LCID(s) of MAC control element(s), MAC controlelement corresponding bitmap, . . . ). Moreover, the numerology and/orTTI information could be replaced by one or multiple informationmentioned in the description of Method 1.

Another possibility could be that network provides SR configurationindex/identity in service configuration related to the MAC controlelement. And the UE triggers SR according to the SR configurationindex/identity for the MAC control element.

Option 3 (All SR configurations can be candidate, and the UE selects oneof them)—Possibly, UE triggers SR transmission according to SRconfiguration which has the closest SR transmission to the MAC controlelement trigger timing. The closest SR transmission may need to take UEprocessing capability into account.

Option 4 (Defined SR configuration for new MAC controlelement)—Possibly, UE will be configured with a SR configuration used todedicatedly handle one or multiple MAC multiple MAC control element(s).There could be more than one SR configurations used to dedicated forhandling the MAC control element(s).

Option 5 (UE could autonomously select one of multiple SRconfigurations, instead of all SR configurations; and the multiple SRconfigurations are decided based on some conditions)—Possibly, UE willbe configured with one or multiple criteria for deciding appropriate setof SR configurations. The criteria could be threshold for TTI lengthand/or numerology. The criteria could be LCG(s).

Applying Method 2

In case 1, possible options for handling how sidelink BSR trigger SR forrequesting uplink resource are as follows:

Option 1 (Pre-defined rule for UE to set multiple bits SR)—Possibly, UEsets multiple bits SR to default or access numerology when sidelink BSRneeds to trigger SR. The default numerology could be default numerologydefined in specification for MAC control element to request resource.The default numerology could be numerology used for receiving systeminformation in RRC_IDLE state and/or RRC_INACTIVE state. The defaultnumerology could be different for different UEs (e.g. NB-IoT UE andnormal UE may have different default numerologies due to UE capability).

Another possibility could be that UE sets multiple bits SR to thelargest or the smallest numerology which the UE can use. The numerologywhich a UE can use will need to take UE capability into account. In oneembodiment, the numerology which a UE can use will also need to takeconfiguration provided from network into account. If the UE does nothave a configuration related to certain numerology, the UE may not beable to transmit SR on that numerology even the UE is capable to use.The configuration could be data transmission related configuration.

Yet another possibility could be that UE sets multiple bits SR torequest all numerologies the UE can use. Moreover, the numerology couldbe replaced by one or multiple TTI/numerology information (e.g. LCGand/or TTI length, etc.) mentioned in the description of Method 2.Alternatively, considering all possible simple rules mentioned above,another possibility could be network configures which rule a UE shallfollow when sidelink BSR is triggered.

Option 2 (Network configures the association between sidelink BSR andmultiple bits SR setting)—Possibly, network could provide numerologyand/or TTI information to a service (e.g. sidelink, MBMS, V2X, V2V,relay, MTC, URLLC, IoT etc.). And a MAC control element related to theservice will set multiple bits SR by similar rule as logical channelwith data. The MAC control element will set multiple bits SR to thenumerology and/or TTI information. The numerology and/or TTI informationcould be provided in service configuration (e.g. sidelink communicationconfiguration, sidelink discovery configuration, etc.).

Another possibility could be that network provides numerology and/or TTIinformation to a MAC control element. The MAC control element will setmultiple bits SR to the numerology and/or TTI information. Moreover, theMAC control element may or may not be limited to only use uplinkresource related to the numerology and/or TTI information fortransmission.

Yet another possibility could be that SR configuration includes how toset MAC control element information (e.g. association between LCID(s) ofMAC control element(s) and multiple bits setting, etc.). Moreover, thenumerology and/or TTI information could be replaced by one or multipleinformation mentioned in the description of Method 1.

Option 3—In this option, all possible setting of multiple bits SR can becandidate. And the UE decides how to set by itself.

Option 4 (Defined dedicated setting of multiple bits SR for controlelement (e.g. Sidelink BSR))—Possibly, UE will be configured with adedicated setting of one or multiple fields in the multiple bits SR forhandling one or multiple MAC control element(s). There could be morethan one dedicated setting used to handle different MAC controlelements.

Option 5 (UE can autonomously select one of multiple settings ofmultiple bits SR, instead of all possible settings)—The multiple SRsettings are decided based on some conditions)—Possibly, UE will beconfigured with one or multiple criteria for deciding appropriate set ofSR settings. The criteria could be threshold for TTI length and/ornumerology. The criteria could be LCG(s).

Option 6 (UE sets multiple bits SR based on logical channel havingdata)—Assuming sidelink logical channel will also be associateddifferent TTI lengths and/or numerologies. In such assumption, UE couldapply solution similar to uplink design. Possibly, UE sets multiple bitsSR to TTI length and/or numerology of highest priority sidelink logicalchannel within all sidelink logical channels having data in all ProSedestinations. Another possibility could be that UE set multiple bits SRto TTI length and/or numerology of sidelink logical channel for latestsidelink BSR triggering.

In case 2, possible options for handling SR triggering for a timerand/or counter controlled based control element are as follows:

Option 1 (Pre-defined rule for UE to set multiple bits SR)—Possibly, UEsets multiple bits SR to default or access numerology when timer/countercontrol based MAC CE needs to trigger SR. The default numerology couldbe default numerology defined in specification for control element torequest resource. The default numerology could be numerology used forreceiving system information in RRC_IDLE state and/or RRC_INACTIVEstate. The default numerology could be different for different UEs (e.g.NB-IoT UE and normal UE may have different default numerologies due toUE capability).

Another possibility could be that UE sets multiple bits SR to thelargest or the smallest numerology which the UE can use. The numerologywhich a UE can use will need to take UE capability into account. In oneembodiment, the numerology which a UE can use will also need to takeconfiguration provided from network into account. If the UE does nothave a configuration related to certain numerology, the UE may not beable to transmit SR on that numerology even the UE is capable to use.The configuration could be data transmission related configuration.

Yet another possibility could be that UE sets multiple bits SR torequest all numerology the UE can use. Moreover, the numerology could bereplaced by one or multiple TTI/numerology information (e.g. LCG and/orTTI length, . . . ) mentioned in the description of Method 2.Alternatively, considering all possible simple rules mentioned above,another possibility could be network configures which rule a UE shallfollow when timer/counter control based MAC CE is triggered.

Option 2 (Network configures the association between timer/countercontrol based MAC CE and multiple bits SR setting)—Possibly, networkcould provide numerology and/or TTI information to a service. And a MACcontrol element related to the service will set multiple bits SR bysimilar rule as logical channel with data. The MAC control element willset multiple bits SR to the numerology and/or TTI information. Thenumerology and/or TTI information could be provided in serviceconfiguration (e.g. sidelink communication configuration, sidelinkdiscovery configuration, etc.).

Another possibility could be that network provides numerology and/or TTIinformation to a MAC control element. The MAC control element will setmultiple bits SR to the numerology and/or TTI information. Moreover, theMAC control element may or may not be limited to only use uplinkresource related to the numerology and/or TTI information fortransmission.

Yet another possibility could be that SR configuration includes how toset MAC control element information (e.g. association between LCID(s) ofMAC control element(s) and multiple bits setting, . . . ). Moreover, thenumerology and/or TTI information could be replaced by one or multipleinformation mentioned in the description of Method 2.

Option 3—In this option, all possible setting of multiple bits SR can becandidate, and UE decides how to set by itself.

Option 4 (Defined dedicated setting of multiple bits SR fortimer/counter control based MAC CE)—Possibly, UE will be configured witha dedicated setting of one or multiple fields in the multiple bits SRfor handling one or multiple control element(s). There could be morethan one dedicated setting used to handle different control elements.

Option 5: UE can autonomously select one of multiple settings ofmultiple bits SR, instead of all possible settings; and the multiple SRsettings are decided based on some conditions—Possibly, UE will beconfigured with one or multiple criteria for deciding appropriate set ofSR settings (e.g. how to set different fields of SR). The criteria couldbe threshold for TTI length and/or numerology. The criteria could beLCG(s).

Option 6 (Set multiple bits SR based on buffer status)—Possibly, UE setsmultiple bits SR based on current which logical channel(s) having data.More specifically, the UE will set multiple bits SR to the TTI and/ornumerology of the highest priority logical channel within all (sidelink)logical channels having data.

Alternatively, the UE will set multiple bits SR to LCG of the highestpriority logical channel within all (sidelink) logical channels havingdata.

Option 7 (Set multiple bits SR based on timer/counterparameter)—Normally, a timer and/or counter will increase or decreasebased on certain time unit. Possibly, a UE set multiple bits SR based onthe time unit. There may be parameters (e.g. 1 slot, 14 OFDM symbols, .. . ) for translate time unit to corresponding numerology and/or TTI.For example, if 1 ms subframe is the time unit of a timer and UEtriggers a control element controlled by the timer, the control elementwill set multiple bits SR to 15 khz numerology.

In case 3, possible options for handling SR triggering for potential newcontrol element are as follows:

Option 1 (Pre-defined rule for UE to set multiple bits SR)—Possibly, UEsets multiple bits SR to default or access numerology when the newcontrol element needs to trigger SR. The default numerology could bedefault numerology defined in specification for control element torequest resource. The default numerology could be numerology used forreceiving system information in RRC_IDLE state and/or RRC_INACTIVEstate. The default numerology could be different for different UEs (e.g.NB-IoT UE and normal UE may have different default numerologies due toUE capability).

Another possibility could be that UE sets multiple bits SR to thelargest or the smallest numerology which the UE can use. The numerologywhich a UE can use will need to take UE capability into account. In oneembodiment, the numerology which a UE can use will also need to takeconfiguration provided from network into account. If the UE does nothave a configuration related to certain numerology, the UE may not beable to transmit SR on that numerology even the UE is capable to use.The configuration could be data transmission related configuration.

Yet another possibility could be that UE sets multiple bits SR torequest all numerology the UE can use. Moreover, the numerology could bereplaced by one or multiple TTI/numerology information (e.g. LCG and/orTTI length, etc) mentioned in the description of Method 2.Alternatively, considering all possible simple rules mentioned above,another possibility could be network configures which rule a UE shallfollow when new MAC control element is triggered.

Option 2 (Network configures the association between the new MAC controlelement and multiple bits SR setting)—Possibly, network could providenumerology and/or TTI information to a service (e.g. sidelink, MBMS,V2X, V2V, relay, MTC, URLLC, IoT etc.). A MAC control element related tothe service will set multiple bits SR by similar rule as logical channelwith data. The MAC control element will set multiple bits SR to thenumerology and/or TTI information. The numerology and/or TTI informationcould be provided in service configuration (e.g. sidelink communicationconfiguration, sidelink discovery configuration, etc).

Another possibility could be that network provides numerology and/or TTIinformation to a MAC control element. The MAC control element will setmultiple bits SR to the numerology and/or TTI information. Moreover, theMAC control element may or may not be limited to only use uplinkresource related to the numerology and/or TTI information fortransmission.

Yet another possibility could be that SR configuration includes how toset MAC control element information (e.g. association between LCID(s) ofMAC control element(s) and multiple bits setting, etc). Moreover, thenumerology and/or TTI information could be replaced by one or multipleinformation mentioned in the description of Method 2.

Option 3—All possible setting of multiple bits SR can be candidate, andthe UE decides how to set by itself.

Option 4 (Defined dedicated setting of multiple bits SR for controlelement)—Possibly, UE will be configured with a dedicated setting of oneor multiple fields in the multiple bits SR for handling one or multiplecontrol element(s). There could be more than one dedicated setting usedto handle different control elements.

Option 5 (UE can autonomously select one of multiple settings ofmultiple bits SR, instead of all possible settings; and the multiple SRsettings are decided based on some conditions)—Possibly, UE will beconfigured with one or multiple criteria for deciding appropriate set ofSR settings. The criteria could be threshold for TTI length and/ornumerology. The criteria could be LCG(s).

Applying Method 3

In case 1, some possible options for handling how sidelink BSR triggerSR for requesting uplink resource are as follows:

Option 1 (Pre-defined rule for UE to select SR configuration and to setmultiple bits SR accordingly)—Possibly, UE triggers and sets SRtransmission according to SR configuration associated with default oraccess numerology when sidelink BSR needs to trigger SR. The defaultnumerology could be default numerology defined in specification forcontrol element to request resource. The default numerology could benumerology used for receiving system information in RRC_IDLE stateand/or RRC_INACTIVE state. The default numerology could be different fordifferent UEs (e.g. NB-IoT UE and normal UE may have different defaultnumerologies due to UE capability).

Another possibility could be that UE always triggers and sets SRtransmission according to SR configuration associated with the largestor the smallest numerology which the UE can use. The numerology which aUE can use will need to take UE capability into account. In oneembodiment, the numerology which a UE can use will also need to takeconfiguration provided from network into account. If the UE does nothave a configuration related to certain numerology, the UE may not beable to transmit SR on that numerology even the UE is capable to use.The configuration could be SR configuration.

Yet another possibility could be that UE always triggers SRconfiguration with the densest SR transmission opportunity. Moreover,the numerology could be replaced by one or multiple TTI/numerologyinformation (e.g. LCG and/or TTI length, etc) mentioned in thedescription of Method 3. Alternatively, considering all possible simplerules mentioned above, another possibility could be network configureswhich rule a UE shall follow when sidelink BSR is triggered.

Option 2 (Network configures the association between sidelink BSR and SRconfiguration and multiple bits SR setting)—Possibly, network couldprovide numerology and/or TTI information to a service (e.g. sidelink,MBMS, V2X, V2V, relay, MTC, URLLC, IoT etc.). A MAC control elementrelated to the service will trigger and set SR transmission by similarrule as logical channel with data. The MAC control element will triggerand set SR transmission according to SR configuration associated withthe numerology and/or TTI information. The numerology and/or TTIinformation could be provided in service configuration (e.g. sidelinkcommunication configuration, sidelink discovery configuration, etc).

Another possibility could be that network provides numerology and/or TTIinformation to a MAC control element. The MAC control element willtrigger SR transmission according to SR configuration associated withthe numerology and/or TTI information. Moreover, the MAC control elementmay or may not be limited to only use uplink resource related to thenumerology and/or TTI information for transmission.

Yet another possibility could be that a SR configuration includes a MACcontrol element information and/or how to set multiple bits SR for theMAC CE (e.g. LCID(s) of MAC control element(s), MAC control elementcorresponding bitmap, etc). Moreover, the numerology and/or TTIinformation could be replaced by one or multiple information mentionedin the description of Method 3.

Another possibility could be that network provides SR configurationindex/identity and/or how to set multiple bits SR in serviceconfiguration related to the MAC control element. And the UE triggers SRaccording to the SR configuration index/identity for the MAC controlelement and also set the multiple bits SR based on the serviceconfiguration.

Option 3 (UE implementation)—All SR configurations and/or multiple bitsSR settings can be candidate. The UE can decide select which SRconfiguration and how to set it.

Option 4 (Defined SR configuration and multiple bits SR setting forcontrol element (e.g. Sidelink BSR))—Possibly, UE will be configured aSR configuration and specific multiple bits SR setting used todedicatedly handle one or multiple control element(s). There could bemore than one SR configuration and/or specific SR setting used todedicated for handling control elements.

Option 5 (UE can autonomously select one of multiple SR configurationsand/or multiple bits SR setting; and the multiple SR configurationsand/or multiple bits SR setting are decided based on someconditions)—Possibly, UE will be configured with one or multiplecriteria for deciding appropriate set of SR configurations and/ormultiple bits SR setting. The criteria could be threshold for TTI lengthand/or numerology. The criteria could be LCG(s).

Option 6 (UE triggers and sets SR transmission according to SRconfiguration associated with logical channel having data)—Assuming thesidelink logical channel will also be associated with different TTIlengths and/or numerologies, the UE can apply solution similar to uplinkdesign. Possibly, UE triggers and sets SR transmission according to SRconfiguration associated with TTI length and/or numerology of highestpriority sidelink logical channel within all sidelink logical channelshaving data in all ProSe destinations.

Another possibility could be that UE triggers and sets SR transmissionaccording to SR configuration associated with TTI length and/ornumerology of sidelink logical channel for latest sidelink BSRtriggering.

In case 2, some possible options for handling SR triggering for a timerand/or counter controlled based control element are as follows:

Option 1 (Pre-defined rule for UE to select SR configuration and to setmultiple bits SR accordingly)—Possibly, UE triggers and sets SRtransmission according to SR configuration associated with default orinitial access numerology when the timer/counter control based MAC CEneeds to trigger SR. The default numerology could be default numerologydefined in specification for control element to request resource. Thedefault numerology could be numerology used for receiving systeminformation in RRC_IDLE state and/or RRC_INACTIVE state. The defaultnumerology could be different for different UEs (e.g. NB-IoT UE andnormal UE may have different default numerologies due to UE capability).

Another possibility could be that UE always triggers and sets SRtransmission according to SR configuration associated with the largestor the smallest numerology which the UE can use. The numerology which aUE can use will need to take UE capability into account. In oneembodiment, the numerology which a UE can use will also need to takeconfiguration provided from network into account. If the UE does nothave a configuration related to certain numerology, the UE may not beable to transmit SR on that numerology even the UE is capable to use.The configuration could be SR configuration.

Yet another possibility could be that UE always triggers SRconfiguration with the densest SR transmission opportunity. Moreover,the numerology could be replaced by one or multiple TTI/numerologyinformation (e.g. LCG and/or TTI length, etc) mentioned in thedescription of Method 3. Alternatively, considering all possible simplerules mentioned above, another possibility could be network configureswhich rule a UE shall follow when new MAC control element is triggered.

Option 2 (Network configures the association between the timer/countercontrol based MAC CE and SR configuration and multiple bits SRsetting)—Possibly, network could provide numerology and/or TTIinformation to a service. A MAC control element related to the servicewill trigger and set SR transmission by similar rule as logical channelwith data. The MAC control element will trigger and set SR transmissionaccording to SR configuration associated with the numerology and/or TTIinformation. The numerology and/or TTI information could be provided inservice configuration (e.g. sidelink communication configuration,sidelink discovery configuration, . . . ).

Another possibility could be that network provides numerology and/or TTIinformation to a MAC control element. The MAC control element willtrigger SR transmission according to SR configuration associated withthe numerology and/or TTI information. Moreover, the MAC control elementmay or may not be limited to only use uplink resource related to thenumerology and/or TTI information for transmission.

Yet another possibility could be that a SR configuration includes a MACcontrol element information and/or how to set multiple bits SR for theMAC CE (e.g. LCID(s) of MAC control element(s), MAC control elementcorresponding bitmap, . . . ). Moreover, the numerology and/or TTIinformation could be replaced by one or multiple information mentionedin the description of Method 3.

Another possibility could be that network provides SR configurationindex/identity and/or how to set multiple bits SR in serviceconfiguration related to the MAC control element. And the UE triggers SRaccording to the SR configuration index/identity for the MAC controlelement and also set the multiple bits SR based on the serviceconfiguration.

Option 3 (UE implementation)—All SR configurations and/or multiple bitsSR settings can be candidate; and the UE can decide select which SRconfiguration and how to set it.

Option 4 (Defined SR configuration and multiple bits SR setting forcontrol element (e.g. Sidelink BSR))—Possibly, UE will be configured aSR configuration and specific multiple bits SR setting used todedicatedly handle one or multiple control element(s). There could bemore than one SR configuration and/or specific SR setting used todedicated for handling MAC control elements.

Option 5 (UE can autonomously select one of multiple SR configurationsand/or multiple bits SR setting, and the multiple SR configurationsand/or multiple bits SR setting are decided based on someconditions)—Possibly, UE will be configured with one or multiplecriteria for deciding appropriate set of SR configurations and/ormultiple bits SR setting. The criteria could be threshold for TTI lengthand/or numerology. The criteria could be LCG(s).

Option 6 (Trigger and set SR based on buffer status)—Possibly, the UEtriggers and sets SR transmission based on which logical channel(s)currently having data. More specifically, the UE will trigger and set SRtransmission according to SR configuration associated with the TTIand/or numerology of the highest priority logical channel within all(sidelink) logical channels having data.

Alternatively, the UE will trigger and set SR transmission according toSR configuration associated with LCG of the highest priority logicalchannel within all (sidelink) logical channels having data.

Option 7 (Trigger and set SR based on timer/counter parameter)—Normally,a timer and/or counter will increase or decrease based on certain timeunit. Possibly, a UE triggers and sets SR transmission according to SRconfiguration associated with the time unit. There may be parameters(e.g. 1 slot, 14 OFDM symbols, . . . ) for translate time unit tocorresponding numerology and/or TTI. For example, if 1 ms subframe isthe time unit of a timer and UE triggers a control element controlled bythe timer, the control element will trigger and set SR transmissionaccording to SR configuration associated with 15 khz numerology.

In case 3, some possible options for handling SR triggering forpotential new control element are as follows:

Option 1 (Pre-defined rule for UE to select SR configuration and to setmultiple bits SR accordingly)—Possibly, the UE triggers and sets SRtransmission according to SR configuration associated with default oraccess numerology when new MAC CE needs to trigger SR. The defaultnumerology could be default numerology defined in specification forcontrol element to request resource. The default numerology could benumerology used for receiving system information in RRC_IDLE stateand/or RRC_INACTIVE state. The default numerology could be different fordifferent UEs (e.g. NB-IoT UE and normal UE may have different defaultnumerologies due to UE capability).

Another possibility could be that UE always triggers and sets SRtransmission according to SR configuration associated with the largestor the smallest numerology which the UE can use. The numerology which aUE can use will need to take UE capability into account. In oneembodiment, the numerology which a UE can use will also need to takeconfiguration provided from network into account. If the UE does nothave a configuration related to certain numerology, the UE may not beable to transmit SR on that numerology even the UE is capable to use.The configuration could be SR configuration.

Yet another possibility could be that UE always triggers SRconfiguration with the densest SR transmission opportunity. Moreover,the numerology could be replaced by one or multiple TTI/numerologyinformation (e.g. LCG and/or TTI length, etc.) mentioned in thedescription of Method 3. Alternatively, considering all possible simplerules mentioned above, another possibility could be network configureswhich rule a UE shall follow when new MAC control element is triggered.

Option 2 (Network configures the association between new MAC CE and SRconfiguration and multiple bits SR setting)—Possibly, network couldprovide numerology and/or TTI information to a service. A MAC controlelement related to the service will trigger and set SR transmission bysimilar rule as logical channel with data. The MAC control element willtrigger and set SR transmission according to SR configuration associatedwith the numerology and/or TTI information. The numerology and/or TTIinformation could be provided in service configuration (e.g. sidelinkcommunication configuration, sidelink discovery configuration, . . . ).

Another possibility could be that network provides numerology and/or TTIinformation to a MAC control element. The MAC control element willtrigger SR transmission according to SR configuration associated withthe numerology and/or TTI information. Moreover, the MAC control elementmay or may not be limited to only use uplink resource related to thenumerology and/or TTI information for transmission.

Yet another possibility could be that a SR configuration includes a MACcontrol element information and/or how to set multiple bits SR for theMAC CE (e.g. LCID(s) of MAC control element(s), MAC control elementcorresponding bitmap, . . . ). Moreover, the numerology and/or TTIinformation could be replaced by one or multiple information mentionedin the description of Method 3.

Another possibility could be that network provides SR configurationindex/identity and/or how to set multiple bits SR in serviceconfiguration related to the MAC control element. And the UE triggers SRaccording to the SR configuration index/identity for the MAC controlelement and also set the multiple bits SR based on the serviceconfiguration.

Option 3 (UE implementation)—All SR configurations and/or multiple bitsSR settings can be candidate; and the UE can decide select which SRconfiguration and how to set it.

Option 4 (Defined SR configuration and multiple bits SR setting forcontrol element (e.g. Sidelink BSR))—Possibly, the UE will be configureda SR configuration and specific multiple bits SR setting used todedicatedly handle one or multiple control element(s). There could bemore than one SR configuration and/or specific SR setting used todedicated for handling control elements.

Option 5 (UE can autonomously select one of multiple SR configurationsand/or multiple bits SR setting, and the multiple SR configurationsand/or multiple bits SR setting are decided based on someconditions)—Possibly, the UE will be configured with one or multiplecriteria for deciding appropriate set of SR configurations and/ormultiple bits SR setting. The criteria could be threshold for TTI lengthand/or numerology. The criteria could be LCG(s).

FIG. 11 is an exemplary illustration of numerology and TTI concept. Asshown in FIG. 11, the numerology is interpreted as sub-carrier spacing(SCS) in this example. The TTI refers to time domain duration of ascheduling (e.g. one or multiple OFDM symbols, millisecond, slot,subframe, . . . ). Alternatively, the numerology could be interpreted asa specific TTI duration in certain SCS. Moreover, a band can besemi-statically separated into different sub-bands for supportingdifferent numerologies in system point of view. From UE point of view,such separation may not be visible. Alternatively, there could be noseparation and network allocate resource on different numerologiesdynamically based on control signal.

FIG. 12 is an example for applying option 2 of method 1 in case 3. Inthe former part, the data of logical channel 1 (LC1) and the data oflogical channel 2 (LC2) triggers uplink BSR independently. The SRconfigurations used by LC1 and LC2 are different for reflecting resourceneed on different numerologies. Moreover, SR configurations couldinclude identity of new MAC CE for establishing association. Based onthe association, in latter part, when the UE triggers new MAC CE andthere is no uplink resource, the UE transmits SR according to SRconfiguration 1. On the other hand, if the UE triggers a sidelink BSRwhen there is no uplink resource, the UE will transmit SR according toSR configuration 2.

FIG. 13 is an example of applying option 2 of method 1 in case 1.Similar to FIG. 12, the association is established by includingnumerology information (i.e. numerology 1) in sidelink serviceconfiguration. When the UE triggers a sidelink BSR and there is nouplink resource, the UE will transmit SR according to SR configuration1.

FIG. 14 is an example of applying option 2 of method 1 in case 3.Similar to previous example, the association is established by mappingtable between numerology and identity of new MAC CE.

FIG. 15 is an example of applying option 2 of method 2 in case 3. The SRincludes two different fields for separately indicating TTI durationneed and numerology need. In former part, the data of logical channel 1and the data of logical channel 2 triggers uplink BSR independently. TheSR transmission for each data arrival event is set in different valuesaccording to the logical channel configuration. In latter part, sincethe new MAC CE also has corresponding logical channel configuration, theSR transmission for forwarding new MAC CE shall be set accordingly.

FIG. 16 is an example of applying option 1 of method 2 in case 3. Inthis example, the UE will select combination of TTI and numerology fordelivering the new MAC CE as soon as possible. Hence, the UE set fieldsin SR to 120 khz SCS and TTI for urgent service.

FIG. 17 is an example of applying option 1 of method 1 in case 3. Inthis example, the UE will trigger and transmit SR of SR configurationrelated to the largest numerology for the new MAC CE. Hence, the UEtransmit SR according to SR configuration 1.

FIG. 18 is an example of applying option 3 of method 1 in case 3. Inthis example, each SR configuration will have its SR transmissionopportunities. The SR transmission opportunities are shown in differenttable with “0” indication. When the UE triggers a new MAC CE, the UEwill select the closest SR transmission opportunities next to thetriggering timing regardless SR configuration. In this example, the SRtransmission opportunity in SR configuration 2 is selected. In differentalternative, the UE may take SR configurations into account. Morespecifically, the UE will not consider all SR configurations whenselecting appropriate SR transmission resource. The UE will precludesome SR configurations based on criteria and/or threshold. The criteriacould be one or multiple information candidate mentioned in thisdisclosure. The threshold could be information a SR configurationassociated with, like numerology, TTI duration, LCG, priority, TB size,etc.

PDCCH Monitoring Discussion

In the current NR design, multiple numerologies are introduced forsupporting variant service requirements and UE capabilities. Morespecifically, different numerologies mean different Single CarrierSpacing (SCS) and can support different TTI durations. Data transmissionon different numerologies will have different latencies due to differentTTI durations. The larger SCS is used the shorter TTI duration issupported.

In LTE, after a UE transmits a SR, the UE needs to keep monitoringcontrol channel (e.g. PDCCH) for receiving corresponding scheduling frombase station until no pending SR exists (or SR is cancelled). Regardingcontrol channel for scheduling numerology of data transmission, somepossible designs can be considered below:

Alternative 1: A control channel on a numerology can only schedule datachannel(s) on the numerology.

Alternative 2: A control channel on a numerology can schedule datachannel(s) on one or multiple numerologies.

Alternative 3: A control channel on a numerology can schedule anynumerology which UE can support and/or UE is configured with.

For alternative 1, a control channel will be associated with specificdata numerology for scheduling. The UE will expect that the dataresource scheduling (e.g. downlink assignment, uplink grant, sidelinkgrant, SPS scheduling, grant-free activation command) received from thecontrol channel is occur on the specific numerology. The associationcould be configured by network (e.g. base station). The associationcould be implicit established. The implicit association could be controlchannel on the same numerology as data channel, on the same sub-band assub-band of data channel on certain numerology, or in same cell as cellof a data channel on certain numerology.

Regarding alternative 2, the association between control channel anddata channel on different numerologies could be implicit or explicit.For instance, in implicit association case, a control channel can beused to schedule data transmission on any numerology larger/smaller andequal to the numerology of control channel. By this way, once UE isconfigured with a control channel, the UE will establish the associationby itself. For another example, in explicit association, when networkprovides configuration of a control channel, the network can associatethe control channel to one or multiple numerologies. One possible way isto include numerology related information (e.g. numerology indexes) intocontrol channel configuration. Other possible ways could be to includethe control channel information (e.g. control channel configurationindex) in numerology related configuration, or to map one or multiplenumerologies of data channel on different cells.

Then the cross carrier scheduling method in LTE can be reused for thispurpose. In carrier aggregation, a control channel can be used toschedule one or multiple cells. Based on the design, the associationbetween control channel and numerology of data channel can beestablished. Moreover, a UE can be configured with multiple controlchannels. Different control channels may use different alternatives(e.g. default control channel uses alternative 3 and additional controlchannel(s) use alternative 2).

For alternative 3, the control channel could schedule data transmissionon any numerology (UE is configured with or UE is capable to use). Thescheduling control message transmitted on a control channel applied withalternative 3 may include information related to numerology of a datatransmission.

Different cases based on the alternatives and the methods for SRreflecting numerology/TTI information are discussed below. And theassumption is based on UE having multiple control resource sets orcalled control channels (e.g. multiple downlink control channels). Eachcontrol resource set could apply one of the three alternatives on datanumerology scheduling. Moreover, the multiple control resource set couldbe allocated for one cell or for carrier aggregation case. The differentcontrol resource sets may be separated from time and/or frequency and/orcode domain.

Method 1+Alternative 1 or Alternative 2

Case 1: Special SR Triggering Event (e.g. Sidelink BSR, Timer and/orCounter Controlled Based Control Element (e.g. Retx-BSR Timer),Potential New Uplink MAC Control Element which can Trigger SR)

Option 1 (Monitoring control channel(s) responsible for schedulingnumerology related to SR configuration(s) with triggered SR)—In thisoption, since each SR configuration is associated with one or multiplenumerologies, the SR transmission based on specific configuration caninform base station about the TTI duration and/or numerology of uplinkneed. It is reasonable for base station to schedule resource based onthe received SR transmission(s). Hence, control channel which canprovide corresponding scheduling should be monitored.

Option 2 (Monitoring control channel(s) responsible for schedulingnumerology related to SR configuration(s) with triggered SR andnumerology larger or smaller than numerology related to the SRconfiguration(s) with triggered SR)—In this option, since each SRconfiguration is associated with one or multiple numerologies, the SRtransmission based on specific configuration can inform base stationabout the TTI duration and/or numerology of uplink need. It would bereasonable for base station to schedule resource based on the receivedSR transmission(s). Hence, control channel which can providecorresponding scheduling should be monitored.

Moreover, for increasing system scheduling flexibility, it is alsobeneficial to allow base station to schedule resource on differentnumerologies or with different TTI durations, instead of onlynumerologies and/or TTI durations informed by SR transmission. Onepossible rule is to let UE also monitor control channel which canschedule numerology smaller or larger than numerologies informationcarried by SR transmission. The range for how large or how small couldbe configured by base station and/or decided based on predefined rule(e.g. until largest or smallest numerology UE is configured with). ForURLLC service, larger numerology resource could be also suitable for aUE from latency perspective. For eMTC service, the smaller numerologycould be suitable for a UE from low complexity perspective andreliability perspective.

Whether the UE will also monitor smaller or larger numerology may bedone as follows:

-   1. Configured by network-   2. Decided by UE itself based on ongoing service and/or current SR    transmission(s) (e.g. SR request TTI/numerology less than a    threshold, SR triggered for certain logical channel(s))-   3. Decided based on UE category/type/complexity-   4. Decided based on UE subscription

Option 3 (Monitoring control channel(s) for all numerologies UE isconfigured with or UE can support)—It is the simplest way for UE todirectly monitor all control channels which the UE can monitor.

Option 4 (Monitoring control channel(s) responsible for scheduling thelargest or smallest numerology related to SR configuration(s) withtriggered SR)—In this option, UE always monitors either largest orsmallest numerology. The largest or smallest numerology could be limitedto those numerologies associated with SR configuration(s) with triggerSR. The network (e.g. base station) will share the same understandingand schedule based on the same rule. By limiting number of controlchannels for monitoring, the power consumption could be reduced.

Moreover, since UE may have multiple control channels for differentnumerologies, UE may monitor other control channel which are not largestor smallest based on conditions other than SR transmission. Theconditions other than SR transmission could be one or multiple optionslisted below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Option 5 (Monitoring control channel(s) which can schedule mostnumerologies related to SR configuration(s) with triggered SR or mostnumerologies UE is configured with or UE can support)—In this option, UEwill select control channel which schedule more numerology for reducingpower consumption on monitoring. The UE may take only those numerologiesrelated to SR configuration(s) with triggered SR into account forcalculating number of numerologies scheduled by a control channel.

Option 6 (Monitoring specific control channel(s) associated with thespecial SR triggering event)—In this option, since UE knows SR istriggered for special event and network will share the sameunderstanding based on received SR, the UE could monitor controlchannel(s) associated with special SR triggering event, instead of allcontrol channels.

The association could be configured by network (e.g. base station). Theassociation could be provided in service configuration (e.g. sidelinkconfiguration), control channel configuration (e.g. include controlelement identity in control channel configuration), cell configuration(e.g. both control channel and control element belong to same cell), orother possible RRC configuration provided through system information ordedicated signaling. For example, a sidelink BSR triggers a SR and theSR is transmitted to the network.

Assuming not all PDCCHs (e.g. all control resource sets) can schedulesidelink resource, if the SR could indicate sidelink BSR existence, theUE will monitor PDCCH(s) which can schedule sidelink resources. Andwhich PDCCH can be used to schedule sidelink resource may be decided bysidelink related configuration (e.g. communication configuration, poolconfiguration, or numerology configuration) and/or cell configuration.

The association could be predefined. For example, UE monitors defaultcontrol channel for special event.

Option 7 (Monitoring control channel(s) for uplink)—In this option,control channels could be separated into two sets or three sets. Thefirst set is used for uplink scheduling. The second set is used fordownlink scheduling. The third set is used for both downlink schedulingand uplink scheduling. After UE transmits SR transmission, the UE willmonitor the first set and/or the third set. Moreover, the second set maybe monitor based on conditions listed below, instead of SR transmissioncondition.

The conditions could be one or multiple options listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Case 2: SR is Triggered by Uplink Data Arrival

Option 1 (Monitoring control channel(s) responsible for schedulingnumerology related to SR configuration(s) with triggered SR)—In thisoption, since each SR configuration is associated with one or multiplenumerologies, the SR transmission based on specific configuration caninform base station about the TTI duration and/or numerology of uplinkneed. It is reasonable for base station to schedule resource based onthe received SR transmission(s). Hence, control channel which canprovide corresponding scheduling should be monitored.

Option 2 (Monitoring control channel(s) responsible for schedulingnumerology related to SR configuration(s) with triggered SR andnumerology larger or smaller than numerology related to the SRconfiguration(s) with triggered SR)—In this option, since each SRconfiguration is associated with one or multiple numerologies, the SRtransmission based on specific configuration can inform base stationabout the TTI duration and/or numerology of uplink need. It isreasonable for base station to schedule resource based on the receivedSR transmission(s). Hence, control channel which can providecorresponding scheduling should be monitored.

Moreover, for increasing system scheduling flexibility, it is alsobeneficial to allow base station to schedule resource on differentnumerologies or with different TTI durations, instead of onlynumerologies and/or TTI durations informed by SR transmission. Onepossible rule is to let UE also monitor control channel which canschedule numerology smaller or larger than numerologies informationcarried by SR transmission. The range for how large or how small couldbe configured by base station and/or decided based on predefined rule(e.g. until largest or smallest numerology UE is configured with). ForURLLC service, larger numerology resource could be also suitable for aUE from latency perspective. For eMTC service, the smaller numerologycould be suitable for a UE from low complexity perspective andreliability perspective.

Whether UE will also monitor smaller or larger numerology may be:

-   1. Configured by network-   2. Decided by UE itself based on ongoing service and/or current SR    transmission(s) (e.g. SR request TTI/numerology less than a    threshold, SR triggered for certain logical channel(s))-   3. Decided based on UE category/type/complexity-   4. Decided based on UE subscription

Option 3 (Monitoring control channel(s) for all numerologies UE isconfigured with or UE can support)—It is the simplest way for UE todirectly monitor all control channels which the UE can monitor.

Option 4 (Monitoring control channel(s) responsible for scheduling thelargest or smallest numerology related to SR configuration(s) withtriggered SR)—In this option, UE always monitors either largest orsmallest numerology. The largest or smallest numerology could be limitedto those numerologies associated with SR configuration(s) with triggerSR. The network (e.g. base station) will share the same understandingand schedule based on the same rule. By limiting number of controlchannels for monitoring, the power consumption could be reduced.

Moreover, since UE may have multiple control channels for differentnumerologies, the UE may monitor other control channel which are notlargest or smallest based on conditions other than SR transmission. Theconditions other than SR transmission could be one or multiple optionslisted below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity-   8. A sidelink grant for a pending HARQ (re-)transmission can occur

Option 5 (Monitoring control channel(s) which can schedule mostnumerologies related to SR configuration(s) with triggered SR or mostnumerologies UE is configured with or UE can support)—In this option, UEwill select control channel which schedule more numerology for reducingpower consumption on monitoring. The UE may take only those numerologiesrelated to SR configuration(s) with triggered SR into account forcalculating number of numerologies scheduled by a control channel.

Option 6 (Monitoring control channel(s) for uplink)—In this option,control channels could be separated into two sets or three sets. Thefirst set is used for uplink scheduling. The second set is used fordownlink scheduling. The third set is used for both downlink schedulingand uplink scheduling. After UE transmits SR transmission, the UE willmonitor the first set and/or the third set. Moreover, the second set maybe monitor based on conditions listed below, instead of SR transmissioncondition.

The conditions could be one or multiple options listed in below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity-   8. A sidelink grant for a pending HARQ (re-)transmission can occur

Method 2+Alternative 1 or Alternative 2

Case 1: Special SR Triggering Event (e.g. Sidelink BSR, Timer and/orCounter Controlled Based Control Element (e.g. Retx-BSR Timer),Potential New Uplink MAC Control Element which can Trigger SR)

Option 1 (Monitoring control channel(s) responsible for schedulingnumerology related to the multiple bits setting of the last SRtransmission)—In this option, since a multiple bits setting isassociated with one or multiple numerologies, a base station canschedule resource based on the received SR transmission(s). Hence,control channel which can provide corresponding numerology schedulingshould be monitored.

Option 2 (Monitoring control channel(s) responsible for schedulingnumerology related to the multiple bits setting of the last SRtransmission and numerology larger or smaller than numerology related tothe multiple bits setting of the last SR transmission)—In this option,since each kind of multiple bits setting in SR is associated with one ormultiple numerologies, the SR transmission based on specificconfiguration can inform base station about the TTI duration and/ornumerology of uplink need. It is reasonable for base station to scheduleresource based on the received SR transmission(s). Hence, controlchannel which can provide corresponding scheduling should be monitored.

Moreover, for increasing system scheduling flexibility, it is beneficialto allow base station to schedule resource on different numerologies orwith different TTI durations, instead of only numerologies and/or TTIdurations informed by SR transmission. One possible rule is to let UEalso monitor control channel which can schedule numerology smaller orlarger than numerologies information carried by SR transmission. Therange for how large or how small could be configured by base stationand/or decided based on predefined rule (e.g. until largest or smallestnumerology UE is configured with). For URLLC service, larger numerologyresource could be also suitable for a UE from latency perspective. ForeMTC service, the smaller numerology could be suitable for a UE from lowcomplexity perspective and reliability perspective.

Whether UE will also monitor smaller or larger numerology may be:

-   1. Configured by network-   2. Decided by UE itself based on ongoing service and/or current SR    transmission(s) (e.g. SR request TTI/numerology less than a    threshold, SR triggered for certain logical channel(s))-   3. Decided based on UE category/type/complexity-   4. Decided based on UE subscription

Moreover, since the UE may have multiple control channels for differentnumerologies, the UE may monitor other control channel which are notlargest or smallest based on conditions other than SR transmission. Theconditions other than SR transmission could be one or multiple optionslisted in below:

Option 4 (Monitoring control channel(s) responsible for scheduling thelargest or smallest numerology related to the multiple bits setting ofthe last SR transmission)—In this option, UE always monitors eitherlargest or smallest numerology. The largest or smallest numerology couldbe limited to those numerologies informed by SR transmission. Thenetwork (e.g. base station) will share the same understanding andschedule based on the same rule. By limiting number of control channelsfor monitoring, the power consumption could be reduced.

Moreover, since the UE may have multiple control channels for differentnumerologies, the UE may monitor other control channel which are notlargest or smallest based on conditions other than SR transmission. Theconditions other than SR transmission could be one or multiple optionslisted in below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity-   8. A sidelink grant for a pending HARQ (re-)transmission can occur

Option 5 (Monitoring control channel(s) which can schedule mostnumerologies related to the multiple bits setting of the last SRtransmission or most numerologies UE is configured with or UE cansupport)—In this option, UE will select control channel which schedulemore numerology for reducing power consumption on monitoring. And the UEmay take only those numerologies informed by SR transmission intoaccount for calculating number of numerologies scheduled by a controlchannel.

Option 6 (Monitoring specific control channel(s) associated with thespecial SR triggering event)—In this option, since the UE knows SR istriggered for special event and network will share the sameunderstanding based on received SR, the UE could monitor controlchannel(s) associated with special SR triggering event, instead of allcontrol channels.

The association could be configured by network (e.g. base station). Theassociation could be provided in service configuration (e.g. sidelinkconfiguration), control channel configuration (e.g. include controlelement identity in control channel configuration), cell configuration(e.g. both control channel and control element belong to same cell), or. . . . For example, a sidelink BSR triggers a SR and the SR istransmitted to the network. Assume not all PDCCHs (e.g. all controlresource sets) can schedule sidelink resource. If the SR could indicatesidelink BSR existence, UE will monitor PDCCH(s) which can schedulesidelink resource. And which PDCCH can be used to schedule sidelinkresource may be decided by sidelink related configuration (e.g.communication configuration, pool configuration, or numerologyconfiguration) and/or cell configuration.

The association could be predefined. For example, UE monitors defaultcontrol channel for special event.

Option 7 (Monitoring control channel(s) for uplink)—In this option,control channels could be separated into two sets or three sets. Thefirst set is used for uplink scheduling. The second set is used fordownlink scheduling. The third set is used for both downlink schedulingand uplink scheduling. After UE transmits SR transmission, the UE willmonitor the first set and/or the third set. Moreover, the second set maybe monitor based on conditions listed below, instead of SR transmissioncondition.

The conditions could be one or multiple options listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. an uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Case 2: SR is Triggered by Uplink Data Arrival

Option 1 (Monitoring control channel(s) responsible for schedulingnumerology related to the multiple bits setting of the last SRtransmission)—In this option, since a multiple bits setting isassociated with one or multiple numerologies, a base station canschedule resource based on the received SR transmission(s). Hence,control channel which can provide corresponding numerology schedulingshould be monitored.

Option 2 (Monitoring control channel(s) responsible for schedulingnumerology related to the multiple bits setting of the last SRtransmission and numerology larger or smaller than numerology related tothe multiple bits setting of the last SR transmission)—In this option,since each kind of multiple bits setting in SR is associated with one ormultiple numerologies, the SR transmission based on specificconfiguration can inform base station about the TTI duration and/ornumerology of uplink need. It is reasonable for base station to scheduleresource based on the received SR transmission(s). Hence, controlchannel which can provide corresponding scheduling should be monitored.

Moreover, for increasing system scheduling flexibility, it is alsobeneficial to allow base station to schedule resource on differentnumerologies or with different TTI durations, instead of onlynumerologies and/or TTI durations informed by SR transmission. Onepossible rule is to let UE also monitor control channel which canschedule numerology smaller or larger than numerologies informationcarried by SR transmission. The range for how large or how small couldbe configured by base station and/or decided based on predefined rule(e.g. until largest or smallest numerology UE is configured with). ForURLLC service, larger numerology resource could be also suitable for aUE from latency perspective. For eMTC service, the smaller numerologycould be suitable for a UE from low complexity perspective andreliability perspective.

Whether UE will also monitor smaller or larger numerology may be:

-   1. Configured by network-   2. Decided by UE itself based on ongoing service and/or current SR    transmission(s) (e.g. SR request TTI/numerology less than a    threshold, SR triggered for certain logical channel(s))-   3. Decided based on UE category/type/complexity-   4. Decided based on UE subscription

Option 3 (Monitoring control channel(s) for all numerologies UE isconfigured with or UE can support)—It is the simplest way for UE todirectly monitor all control channels which the UE can monitor.

Option 4 (Monitoring control channel(s) responsible for scheduling thelargest or smallest numerology related to the multiple bits setting ofthe last SR transmission)—In this option, UE always monitors eitherlargest or smallest numerology. The largest or smallest numerology couldbe limited to those numerologies informed by SR transmission. Thenetwork (e.g. base station) will share the same understanding andschedule based on the same rule. By limiting number of control channelsfor monitoring, the power consumption could be reduced.

Moreover, since the UE may have multiple control channels for differentnumerologies, the UE may monitor other control channel which are notlargest or smallest based on conditions other than SR transmission. Theconditions other than SR transmission could be one or multiple optionslisted in below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Option 5 (Monitoring control channel(s) which can schedule mostnumerologies related to the multiple bits setting of the last SRtransmission or most numerologies UE is configured with or UE cansupport)—In this option, UE will select control channel which schedulemore numerology for reducing power consumption on monitoring. The UE maytake only those numerologies informed by SR transmission into accountfor calculating number of numerologies scheduled by a control channel.

Option 6 (Monitoring control channel(s) for uplink)—In this option,control channels could be separated into two sets or three sets. Thefirst set is used for uplink scheduling. The second set is used fordownlink scheduling. The third set is used for both downlink schedulingand uplink scheduling. After UE transmits SR transmission, the UE willmonitor the first set and/or the third set. Moreover, the second set maybe monitor based on conditions listed below, instead of SR transmissioncondition.

The conditions could be one or multiple options listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. an uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Method 3+Alternative 1 or Alternative 2

Case 1: Special SR Triggering Event (e.g. Sidelink BSR, Timer and/orCounter Controlled Based Control Element (e.g. Retx-BSR Timer),Potential New Uplink MAC Control Element which can Trigger SR)

Option 1 (Monitoring control channel(s) responsible for schedulingnumerology related to each SR configuration with triggered SR and/or themultiple bits setting of the last SR transmission of each SRconfiguration)—In this option, since a multiple bits SR transmissionbased on a SR configuration is associated with one or multiplenumerologies, the SR transmission can inform base station about the TTIduration and/or numerology of uplink need. It is reasonable for basestation to schedule resource based on the received SR transmission(s).Hence, control channel which can provide corresponding scheduling shouldbe monitored.

Option 2 (Monitoring control channel(s) responsible for schedulingnumerology related to each SR configuration with triggered SR and/or themultiple bits setting of the last SR transmission of each SRconfiguration, and numerology larger or smaller than numerology relatedto each SR configuration with triggered SR and/or the multiple bitssetting of the last SR transmission of each SR configuration)—In thisoption, since a multiple bits SR transmission based on a SRconfiguration is associated with one or multiple numerologies, the SRtransmission based on specific configuration can inform base stationabout the TTI duration and/or numerology of uplink need. It would bereasonable for base station to schedule resource based on the receivedSR transmission(s). Hence, control channel which can providecorresponding scheduling should be monitored.

Moreover, for increasing system scheduling flexibility, it is alsobeneficial to allow base station to schedule resource on differentnumerologies or with different TTI durations, instead of onlynumerologies and/or TTI durations informed by SR transmission. Onepossible rule is to let UE also monitor control channel which canschedule numerology smaller or larger than numerologies informationcarried from SR transmission. The range for how large or how small couldbe configured by base station and/or decided based on predefined rule(e.g. until largest or smallest numerology UE is configured with). ForURLLC service, larger numerology resource could be also suitable for aUE from latency perspective. For eMTC service, the smaller numerologycould be suitable for a UE from low complexity perspective andreliability perspective.

Whether UE will also monitor smaller or larger numerology may be:

-   1. Configured by network.-   2. Decided by UE itself based on ongoing service and/or current SR    transmission(s) (e.g. SR request TTI/numerology less than a    threshold, SR triggered for certain logical channel(s))-   3. Decided based on UE category/type/complexity-   4. Decided based on UE subscription

Option 3 (Monitoring control channel(s) for all numerologies UE isconfigured with or UE can support)—It is the simplest way for UE todirectly monitor all control channels which the UE can monitor.

Option 4 (Monitoring control channel(s) responsible for scheduling thelargest or smallest numerology related to SR configuration(s) withtriggered SR and/or the multiple bits setting of the last SRtransmission of each SR configuration)—In this option, UE alwaysmonitors either largest or smallest numerology. The largest or smallestnumerology could be limited to those numerologies informed by SRtransmission. The network (e.g. base station) will share the sameunderstanding and schedule based on the same rule. By limiting number ofcontrol channels for monitoring, the power consumption could be reduced.

Moreover, since the UE may have multiple control channels for differentnumerologies, the UE may monitor other control channel which are notlargest or smallest based on conditions other than SR transmission. Theconditions other than SR transmission could be one or multiple optionslisted below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Option 5 (Monitoring control channel(s) which can schedule mostnumerologies related to SR configuration(s) with triggered SR and/or themultiple bits setting of the last SR transmission of each SRconfiguration, or most numerologies UE is configured with or UE cansupport)—In this option, the UE will select control channel whichschedule more numerology for reducing power consumption on monitoring.The UE may take only those numerologies informed by SR transmission intoaccount for calculating number of numerologies scheduled by a controlchannel.

Option 6 (Monitoring specific control channel(s) associated with thespecial SR triggering event)—In this option, since UE knows SR istriggered for special event and network will share the sameunderstanding based on received SR, the UE could monitor controlchannel(s) associated with special SR triggering event, instead of allcontrol channels.

The association could be configured by network (e.g. base station). Theassociation could be provided in service configuration (e.g. sidelinkconfiguration), control channel configuration (e.g. include controlelement identity in control channel configuration), cell configuration(e.g. both control channel and control element belong to same cell), or. . . . For example, a sidelink BSR triggers a SR and the SR istransmitted to the network. Assuming not all PDCCH can schedule sidelinkresource, if the SR could indicate sidelink BSR existence, the UE willmonitor PDCCH(s) which can schedule sidelink resource. And which PDCCHcan be used to schedule sidelink resource may be decided by sidelinkrelated configuration (e.g. communication configuration, poolconfiguration, or numerology configuration) and/or cell configuration.

The association could be predefined. For example, UE monitors defaultcontrol channel for special event.

Option 7 (Monitoring control channel(s) for uplink)—In this option,control channels could be separated into two sets or three sets. Thefirst set is used for uplink scheduling. The second set is used fordownlink scheduling. The third set is used for both downlink schedulingand uplink scheduling. After the UE transmits SR transmission, the UEwill monitor the first set and/or the third set. Moreover, the secondset may be monitor based on conditions listed below, instead of SRtransmission condition.

The conditions could be one or multiple options listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Case 2: SR is Triggered by Uplink Data Arrival

Option 1 (Monitoring control channel(s) responsible for schedulingnumerology related to each SR configuration with triggered SR and/or themultiple bits setting of the last SR transmission of each SRconfiguration)—In this option, since a multiple bits SR transmissionbased on a SR configuration is associated with one or multiplenumerologies, the SR transmission can inform base station about the TTIduration and/or numerology of uplink need. It would be reasonable forbase station to schedule resource based on the received SRtransmission(s). Hence, control channel which can provide correspondingscheduling should be monitored.

Option 2 (Monitoring control channel(s) responsible for schedulingnumerology related to each SR configuration with triggered SR and/or themultiple bits setting of the last SR transmission of each SRconfiguration, and numerology larger or smaller than numerology relatedto each SR configuration with triggered SR and/or the multiple bitssetting of the last SR transmission of each SR configuration)—In thisoption, since a multiple bits SR transmission based on a SRconfiguration is associated with one or multiple numerologies, the SRtransmission based on specific configuration can inform base stationabout the TTI duration and/or numerology of uplink need. It isreasonable for base station to schedule resource based on the receivedSR transmission(s). Hence, control channel which can providecorresponding scheduling should be monitored.

Moreover, for increasing system scheduling flexibility, it is alsobeneficial to allow base station to schedule resource on differentnumerologies or with different TTI durations, instead of onlynumerologies and/or TTI durations informed by SR transmission. Onepossible rule is to let UE also monitor control channel which canschedule numerology smaller or larger than numerologies informationcarried from SR transmission. The range for how large or how small couldbe configured by base station and/or decided based on predefined rule(e.g. until largest or smallest numerology UE is configured with). ForURLLC service, larger numerology resource could be also suitable for aUE from latency perspective. For eMTC service, the smaller numerologycould be suitable for a UE from low complexity perspective andreliability perspective.

Whether UE will also monitor smaller or larger numerology may be:

-   1. Configured by network.-   2. Decided by UE itself based on ongoing service and/or current SR    transmission(s) (e.g. SR request TTI/numerology less than a    threshold, SR triggered for certain logical channel(s))-   3. Decided based on UE category/type/complexity-   4. Decided based on UE subscription

Option 3 (Monitoring control channel(s) for all numerologies UE isconfigured with or UE can support)—It is the simplest way for UE todirectly monitor all control channels which the UE can monitor.

Option 4 (Monitoring control channel(s) responsible for scheduling thelargest or smallest numerology related to SR configuration(s) withtriggered SR and/or the multiple bits setting of the last SRtransmission of each SR configuration)—In this option, the UE alwaysmonitors either largest or smallest numerology. The largest or smallestnumerology could be limited to those numerologies informed by SRtransmission. The network (e.g. base station) will share the sameunderstanding and schedule based on the same rule. By limiting number ofcontrol channels for monitoring, the power consumption could be reduced.

Moreover, since the UE may have multiple control channels for differentnumerologies, the UE may monitor other control channel which are notlargest or smallest based on conditions other than SR transmission. Theconditions other than SR transmission could be one or multiple optionslisted below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Option 5 (Monitoring control channel(s) which can schedule mostnumerologies related to SR configuration(s) with triggered SR and/or themultiple bits setting of the last SR transmission of each SRconfiguration, or most numerologies UE is configured with or UE cansupport)—In this option, the UE will select control channel whichschedule more numerology for reducing power consumption on monitoring.The UE may take only those numerologies informed by SR transmission intoaccount for calculating number of numerologies scheduled by a controlchannel.

Option 6 (Monitoring control channel(s) for uplink)—In this option,control channels could be separated into two sets or three sets. Thefirst set is used for uplink scheduling. The second set is used fordownlink scheduling. The third set is used for both downlink schedulingand uplink scheduling. After the UE transmits SR transmission, the UEwill monitor the first set and/or the third set. Moreover, the secondset may be monitor based on conditions listed below, instead of SRtransmission condition.

The conditions could be one or multiple options listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Method 1+Alternative 3

Case 1: Special SR Triggering Event (e.g. Sidelink BSR, Timer and/orCounter Controlled Based Control Element (e.g. Retx-BSR Timer),Potential New Uplink MAC Control Element which can Trigger SR)

Option 1 (Monitoring all control channel(s) UE is configured with)—TheUE just monitors all configured control channels.

Option 2 (Monitoring specific control channel(s) for each SRconfiguration with triggered SR)—In this option, a control channel willbe associated with a SR configuration. Hence, after a UE transmits a SRbased on a SR configuration, the UE will monitor the associated controlchannel. The association could be established based on cellconfiguration, service configuration (e.g. sidelink configuration, V2Xconfiguration), control channel configuration, SR configuration, or MACconfiguration. By this way, UE can reduce control resource set(s) formonitoring for reducing power consumption.

Option 3 (Monitoring specific control channel(s) associated with thespecial SR triggering event)—In this option, since the UE knows SR istriggered for special event and network will share the sameunderstanding based on received SR, the UE could monitor controlchannel(s) associated with special SR triggering event, instead of allcontrol channels (e.g. all control resource sets configured to the UE).

The association could be configured by network (e.g. base station). Theassociation could be provided in service configuration (e.g. sidelinkconfiguration), control channel configuration (e.g. include controlelement identity in control channel configuration), cell configuration(e.g. both control channel and control element belong to same cell), or. . . . For example, a sidelink BSR triggers a SR and the SR istransmitted to the network. Assuming not all PDCCH (e.g. all controlresource sets configured to the UE) can schedule sidelink resource, ifthe SR could indicate sidelink BSR existence, the UE will monitorPDCCH(s) which can schedule sidelink resource. And which PDCCH can beused to schedule sidelink resource may be decided by sidelink relatedconfiguration (e.g. communication configuration, pool configuration, ornumerology configuration) and/or cell configuration.

The association could be predefined. For example, the UE monitorsdefault control channel for the special event.

Option 4 (Monitoring specific control channel(s) (e.g. default controlchannel, configured by network, control channels for uplink scheduling)regardless SR triggering event)—In this option, the UE will monitorspecific control channel(s) regardless information carried by SRtransmission.

The specific control channel could be configured by network ordetermined by predefined rule. For example, if a UE is configured withcontrol channel A, B, C, network could further configure the UE tomonitor only control channel A and B after performing SR transmissionand SR is still pending in the UE. The UE may apply this mechanism aftercertain period is passed (e.g. controlled by a timer or counter). Bythis way, UE can reduce power consumption on control channel monitoring.For another example, a UE will monitor default numerology afterperforming SR transmission and SR is still pending in the UE.

In one embodiment, the UE monitor only default numerology may becontrolled by a timer as previous example. For another example, ifcontrol channel is used for different link scheduling (e.g. downlink,uplink, sidelink, relay link, . . . ), a UE should monitor controlchannel for uplink after performing SR transmission and SR is stillpending in the UE.

Moreover, the UE may monitor other control channel(s) based on one ormultiple conditions listed in DRX mechanism for monitoring PDCCH, exceptfor the SR triggering condition. The possible candidates for theconditions are listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Case 2: SR is Triggered by Uplink Data Arrival

Option 1 (Monitoring all control channel(s) UE is configured with)—TheUE just monitors all configured control channels.

Option 2 (Monitoring specific control channel(s) for each SRconfiguration with triggered SR)—In this option, a control channel willbe associated with a SR configuration. Hence, after a UE transmits a SRbased on a SR configuration, the UE will monitor the associated controlchannel. The association could be established based on cellconfiguration, service configuration (e.g. sidelink configuration, V2Xconfiguration), control channel configuration, SR configuration, or MACconfiguration. By this way, the UE can reduce control resource set formonitoring for reducing power consumption.

Option 3 (Monitoring specific control channel (e.g. default controlchannel, configured by network) regardless SR triggering event)—In thisoption, the UE will monitor specific control channel(s) regardlessinformation carried by SR transmission.

The specific control channel could be configured by network ordetermined by predefined rule. For example, if a UE is configured withcontrol channel A, B, C, network could further configure the UE tomonitor only control channel A and B after performing SR transmissionand SR is still pending in the UE. The UE may apply this mechanism aftercertain period is passed (e.g. controlled by a timer or counter). Bythis way, UE can reduce power consumption on control channel monitoring.For another example, a UE will monitor default numerology afterperforming SR transmission and SR is still pending in the UE. The UEmonitor only default numerology may be controlled by a timer as previousexample. For another example, if control channel is used for differentlink scheduling (e.g. downlink, uplink, sidelink, relay link, etc.), aUE should monitor control channel for uplink after performing SRtransmission and SR is still pending in the UE.

Moreover, the UE may monitor other control channel(s) based on one ormultiple conditions listed in DRX mechanism for monitoring PDCCH, exceptfor the SR triggering condition. The possible candidates for theconditions are listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Method 2+Alternative 3

Case 1: Special SR Triggering Event (e.g. Sidelink BSR, Timer and/orCounter Controlled Based Control Element (e.g. Retx-BSR Timer),Potential New Uplink MAC Control Element which can Trigger SR)

Option 1 (Monitoring all control channel(s) UE is configured with)—TheUE just monitors all configured control channels.

Option 2 (Monitoring specific control channel(s) for each SRconfiguration with triggered SR)—In this option, a control channel willbe associated with a SR configuration. Hence, after a UE transmits a SRbased on a SR configuration, the UE will monitor the associated controlchannel. The association could be established based on cellconfiguration, service configuration (e.g. sidelink configuration, V2Xconfiguration), control channel configuration, SR configuration, or MACconfiguration. By this way, the UE can reduce control resource set formonitoring for reducing power consumption.

Option 3 (Monitoring specific control channel(s) associated with thespecial SR triggering event)—In this option, since the UE knows SR istriggered for special event and network will share the sameunderstanding based on received SR, the UE could monitor controlchannel(s) (e.g. control resource sets) associated with special SRtriggering event, instead of all control channels.

The association could be configured by network (e.g. base station). Theassociation could be provided in service configuration (e.g. sidelinkconfiguration), control channel configuration (e.g. include controlelement identity in control channel configuration), cell configuration(e.g. both control channel and control element belong to same cell), orMAC configuration. For example, a sidelink BSR triggers a SR and the SRis transmitted to the network.

Assuming not all PDCCHs (e.g. control resource sets configured to theUE) can schedule sidelink resource, if the SR could indicate sidelinkBSR existence, the UE will monitor PDCCH(s) which can schedule sidelinkresource. And which PDCCH can be used to schedule sidelink resource maybe decided by sidelink related configuration (e.g. communicationconfiguration, pool configuration, or numerology configuration) and/orcell configuration.

The association could be predefined. For example, UE monitors defaultcontrol channel for special event.

Option 4 (Monitoring specific control channel (e.g. default controlchannel, configured by network) regardless SR triggering event)—In thisoption, the UE will monitor specific control channel(s) regardlessinformation carried by SR transmission.

The specific control channel could be configured by network ordetermined by predefined rule. For example, if a UE is configured withcontrol channel A, B, C, network could further configure the UE tomonitor only control channel A and B after performing SR transmissionand SR is still pending in the UE. The UE may apply this mechanism aftercertain period is passed (e.g. controlled by a timer or counter). Bythis way, UE can reduce power consumption on control channel monitoring.For another example, a UE will monitor default numerology afterperforming SR transmission and SR is still pending in the UE. The UEmonitor only default numerology may be controlled by a timer as previousexample. For another example, if control channel is used for differentlink scheduling (e.g. downlink, uplink, sidelink, relay link, etc.), aUE should monitor control channel for uplink after performing SRtransmission and SR is still pending in the UE.

Moreover, the UE may monitor other control channel(s) based on one ormultiple conditions listed in DRX mechanism for monitoring PDCCH, exceptfor the SR triggering condition. Possible options for the conditions arelisted below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Case 2: SR is Triggered by Uplink Data Arrival

Option 1 (Monitoring all control channel(s) UE is configured with)—TheUE just monitors all configured control channels.

Option 2 (Monitoring specific control channel(s) for each SRconfiguration with triggered SR)—In this option, a control channel willbe associated with a SR configuration. Hence, after a UE transmits a SRbased on a SR configuration, the UE will monitor the associated controlchannel. The association could be established based on cellconfiguration, service configuration (e.g. sidelink configuration, V2Xconfiguration), control channel configuration, SR configuration, or MACconfiguration. By this way, the UE can reduce control resource set formonitoring for reducing power consumption.

Option 3 (Monitoring specific control channel (e.g. default controlchannel, configured by network) regardless SR triggering event)—In thisoption, the UE will monitor specific control channel(s) regardlessinformation carried by SR transmission.

The specific control channel could be configured by network ordetermined by predefined rule. For example, if a UE is configured withcontrol channel A, B, C, network could further configure the UE tomonitor only control channel A and B after performing SR transmissionand SR is still pending in the UE. The UE may apply this mechanism aftercertain period is passed (e.g. controlled by a timer/counter). By thisway, UE can reduce power consumption on control channel monitoring.

As another example, a UE will monitor default numerology afterperforming SR transmission and SR is still pending in the UE. The UEmonitor only default numerology may be controlled by a timer as previousexample.

As yet another example, if control channel is used for different linkscheduling (e.g. downlink, uplink, sidelink, relay link, etc.), a UEshould monitor control channel for uplink after performing SRtransmission and SR is still pending in the UE.

Moreover, the UE may monitor other control channel(s) (e.g. othercontrol resource sets) based on one or multiple conditions listed in DRXmechanism for monitoring PDCCH, except for the SR triggering condition.Possible candidates for the conditions are listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Method 3+Alternative 3

Case 1: Special SR Triggering Event (e.g. Sidelink BSR, Timer and/orCounter Controlled Based Control Element (e.g. Retx-BSR Timer),Potential New Uplink MAC Control Element which can Trigger SR)

Option 1 (Monitoring all control channel(s) UE is configured with)—TheUE just monitors all configured control channels.

Option 2 (Monitoring specific control channel(s) for each SRconfiguration with triggered SR)—In this option, a control channel willbe associated with a SR configuration. Hence, after a UE transmits a SRbased on a SR configuration, the UE will monitor the associated controlchannel. The association could be established based on cellconfiguration, service configuration (e.g. sidelink configuration, V2Xconfiguration), control channel configuration, SR configuration, or MACconfiguration. By this way, the UE can reduce control resource set(s)for monitoring for reducing power consumption.

Option 3 (Monitoring specific control channel(s) associated with thespecial SR triggering event)—In this option, since UE knows SR istriggered for special event and network will share the sameunderstanding based on received SR, the UE could monitor controlchannel(s) associated with special SR triggering event, instead of allcontrol channels.

The association could be configured by network (e.g. base station). Theassociation could be provided in service configuration (e.g. sidelinkconfiguration), control channel configuration (e.g. include controlelement identity in control channel configuration), cell configuration(e.g. both control channel and control element belong to same cell), orMAC configuration. For example, a sidelink BSR triggers a SR and the SRis transmitted to the network. Assuming not all PDCCH can schedulesidelink resource, if the SR could indicate sidelink BSR existence, theUE will monitor PDCCH(s) which can schedule sidelink resource. And whichPDCCH can be used to schedule sidelink resource may be decided bysidelink related configuration (e.g. communication configuration, poolconfiguration, or numerology configuration) and/or cell configuration.

The association could be predefined. For example, the UE monitorsdefault control channel for special event.

Option 4 (Monitoring specific control channel (e.g. default controlchannel, configured by network) regardless SR triggering event)—In thisoption, the UE will monitor specific control channel(s) regardlessinformation carried by SR transmission.

The specific control channel could be configured by network ordetermined by predefined rule. For example, if a UE is configured withcontrol channel A, B, C, network could further configure the UE tomonitor only control channel A and B after performing SR transmissionand SR is still pending in the UE. The UE may apply this mechanism aftercertain period is passed (e.g. controlled by a timer or counter). Bythis way, UE can reduce power consumption on control channel monitoring.For another example, a UE will monitor default numerology afterperforming SR transmission and SR is still pending in the UE. The UEmonitor only default numerology may be controlled by a timer as previousexample.

As another example, if control channel is used for different linkscheduling (e.g. downlink, uplink, sidelink, relay link, etc.), a UEshould monitor control channel for uplink after performing SRtransmission and SR is still pending in the UE. Moreover, the UE maymonitor other control channel(s) based on one or multiple conditionslisted in DRX mechanism for monitoring PDCCH, except for the SRtriggering condition. Possible candidates for the conditions are listedbelow:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Case 2: SR is Triggered by Uplink Data Arrival

Option 1 (Monitoring all control channel(s) UE is configured with)—TheUE just monitors all configured control channels.

Option 2: (Monitoring specific control channel(s) for each SRconfiguration with triggered SR)—In this option, a control channel willbe associated with a SR configuration. Hence, after a UE transmits a SRbased on a SR configuration, the UE will monitor the associated controlchannel. The association could be established based on cellconfiguration, service configuration (e.g. sidelink configuration, V2Xconfiguration), control channel configuration, SR configuration, or MACconfiguration. By this way, the UE can reduce control resource set formonitoring for reducing power consumption.

Option 3 (Monitoring specific control channel (e.g. default controlchannel, configured by network) regardless SR triggering event)—In thisoption, UE will monitor specific control channel(s) regardlessinformation carried by SR transmission.

The specific control channel could be configured by network ordetermined by predefined rule. For example, if a UE is configured withcontrol channel A, B, C, network could further configure the UE tomonitor only control channel A and B after performing SR transmissionand SR is still pending in the UE. The UE may apply this mechanism aftercertain period is passed (e.g. controlled by a timer/counter). By thisway, UE can reduce power consumption on control channel monitoring.

As another example, a UE will monitor default numerology afterperforming SR transmission and SR is still pending in the UE. The UEmonitor only default numerology may be controlled by a timer as previousexample.

As yet another example, if control channel is used for different linkscheduling (e.g. downlink, uplink, sidelink, relay link, . . . ), a UEshould monitor control channel for uplink after performing SRtransmission and SR is still pending in the UE.

Moreover, the UE may monitor other control channel(s) based on one ormultiple conditions listed in DRX mechanism for monitoring PDCCH, exceptfor the SR triggering condition. Possible candidates for the conditionsare listed below:

-   1. DurationTimer is running-   2. drx-InactivityTimer is running-   3. drx-RetransmissionTimer is running-   4. drx-ULRetransmissionTimer is running-   5. ContentionResolutionTimer is running-   6. An uplink grant for a pending HARQ retransmission can occur and    there is data in the corresponding HARQ buffer for synchronous HARQ    process-   7. A PDCCH indicating a new transmission addressed to the C-RNTI of    the MAC entity has not been received after successful reception of a    Random Access Response for the preamble not selected by the MAC    entity.-   8. A sidelink grant for a pending HARQ (re-)transmission can occur.

Furthermore, the case for uplink data arrival and cases for each specialSR trigging event could apply different options on PDCCH monitoring.

For example, for uplink data arrival case, the UE could apply monitoringall control channels or corresponding control channel for schedulingnumerology related to numerology information carried by SR transmission,while special event applies option 3 for monitoring specific controlchannel(s) associated with the special SR triggering event. In thiscase, SR transmission will indicate special event based on setting ofmultiple bits SR and/or which SR configuration is used.

As another example, the UE monitors control channels for uplink inuplink data arrival cases, and the UE monitors all control channels fora special SR triggering event case (e.g. sidelink BSR or retxBSR timerexpiry or new control element).

For different special SR triggering events, the UE could also applydifferent options. For example, the UE could apply specific controlmonitoring for sidelink BSR case, and all control channels monitoringfor retxBSR timer expiry case and corresponding scheduling controlchannel to information carried by SR for uplink data arrival case.

Moreover, regarding PDCCH monitoring period, one possibility is to keepmonitoring control channel(s) responsible for scheduling numerologyrelated to SR configuration(s) with triggered SR after SR of the SRconfiguration is transmitted and until SR of the SR configuration iscancelled (e.g. no pending SR for the SR configuration) or SRs of all SRconfiguration with triggered SR are cancelled (e.g. no pending SR in theUE). Another possibility is to monitor control channel(s) responsiblefor scheduling numerology related to a SR configuration with triggeredSR within certain period (e.g. control by timer) after performingcorresponding SR transmission.

An additional possibility is to monitor one or multiple control channelsregardless SR of which SR configuration with triggered SR beingtransmitted. The possibility mentioned above could also be applied ondifferent control channels at the same time. For example, for a controlchannel (e.g. default control channel), a UE monitors the controlchannel after the UE performs a SR transmission. The UE will furthermonitor another control channel after the UE performs a SR transmission.In addition, the UE will monitor another control channel within certainperiod instead of monitoring till no SR pending.

The default control channel could be defined by one or multiplecondition(s) below:

-   1. Control channel on PCell-   2. Control channel used to monitor Paging message-   3. Control channel used to monitor SI-RNTI-   4. Control channel used for scheduling default numerology-   5. Control channel with very first index or very last index

The SR configuration with triggered SR refers to a SR configuration thathas pending SR and UE already performs SR transmission once based on theSR configuration since last SR cancellation for the SR configuration. Anexample is shown in FIG. 19. In particular, FIG. 19 shows an exemplaryembodiment of a PDCCH monitoring period of a SR configuration withtriggered SR. The grey period in FIG. 19 is the PDCCH monitoring periodfor SR configuration 1 with triggered SR. The black period in FIG. 19 isthe PDCCH monitoring period for SR configuration 2 with triggered SR.

As shown in FIG. 19, the UE starts to monitor control channel (e.g.PDCCH) for a SR configuration with triggered SR, when UE performs a SRtransmission based on the SR configuration and there is SR pending forthe SR configuration or for all SR configurations or in the UE.

The control channel could be a PDCCH. The control channel could bedownlink control channel (e.g. ePDCCH, sPDCCH, etc.). The controlchannel could be a control resource set. The control channel is adownlink channel which UE can receives control signalling for schedulingresource to a data transmission.

FIG. 20 is an example of applying option 1 for method 1 and alternative1 in case 2. There are two SR configurations and two control channels(in front part and arrow means numerology can be scheduled by thecontrol channel). Each SR configuration is associated with one uplinkdata numerology need. When the UE performs SR transmission in the secondtransmission opportunity of the SR configuration on the top, the UE willmonitor the control channel in deep grey.

FIG. 21 is an example for applying option 6 for method 2 and alternative1 in case 1. A UE transmits a SR with multiple bits SR to a basestation. The multiple bits SR shows existence of a sidelink BSR. Thenetwork will implicitly understand to schedule uplink resource on thecontrol channel which can also schedule sidelink resource. On the otherhand, if the multiple bits SR shows numerology for uplink data arrivalcase, the UE could monitor control channel following rule in previousexample.

FIG. 22 is an example for applying option 3 for method 1 and alternative1 in case 1. When the UE performs SR transmission in the secondtransmission opportunity of the SR configuration on the top, the UE willmonitor all control channels (in deep grey).

FIG. 23 is an example for applying option 6 of method 2 and alternative1 in case 1. A UE transmits a SR with multiple bits SR to a basestation. The multiple bits SR shows existence of a new MAC CE. Since acontrol channel is associated with the new MAC CE, the UE just monitorsthe control channel (in deep grey).

FIG. 24 is an example for applying option 4 of method 1 and alternative1 in case 2. There are two SR configurations and two control channels(in front part and arrow means numerology can be scheduled by thecontrol channel). Each SR configuration is associated with one ormultiple uplink data numerology need. When the UE performs SRtransmission based on the second SR configuration, the UE will monitorthe control channel in deep grey. Assuming the second SR configurationis related to data numerology in the middle, the UE will monitor controlchannels (in deep drey) for scheduling numerology in the middle andnumerology larger than middle.

FIG. 25 is an example for applying option 2 of method 1 and alternative3 in case 2. There are two SR configurations and two control channels(in front part and arrow means numerology can be scheduled by thecontrol channel). Each SR configuration is associated with one uplinkdata numerology need. When the UE performs SR transmission in the secondtransmission opportunity of the SR configuration on the top, the UE willmonitor the control channel in deep grey because the control channel isassociated with the SR configuration 1.

FIG. 26 is an example for applying option 4 of method 1 and alternative3 in case 1. There are two SR configurations and two control channels(in front part and arrow means numerology can be scheduled by thecontrol channel). Each SR configuration is associated with one uplinkdata numerology need. When the UE performs SR transmission in the secondtransmission opportunity of the SR configuration on the top, the UE willmonitor the control channel in deep grey because the control channel isdefault control channel.

FIG. 27 is an example for applying Alternative 1 on all controlchannel(s). In particular, FIG. 27 illustrates a one-to-one mappingbetween a control channel and scheduling of data numerology. As shown inFIG. 27, each control channel (shown as a deep grey portion) canschedule data transmission on specific numerology.

FIG. 28 is an example for applying Alternative 3 on all controlchannel(s). In particular, FIG. 28 illustrates a one-to-one mappingbetween a control channel and scheduling of data numerology. The controlchannel (shown as a deep grey portion) can schedule data transmission onthree different numerologies.

FIG. 29 is an example for applying Alternative 2 on control channel(s).In particular, FIG. 29 illustrates a one-to-one mapping between acontrol channel and scheduling of data numerology. The control channelon the top is configured to be able to schedule data transmission onmultiple numerologies, while other two control channels are configuredto be able to schedule data transmission on specific numerology.

FIG. 30 is an example for applying both alternative 1 and Alternative 2on control channel(s). In particular, FIG. 30 illustrates a one-to-onemapping between a control channel and scheduling of data numerology. Thecontrol channel on the top is applied with alternative 2, while othertwo control channels are applied with alternative 1.

SR Update mechanism

How to transmit SR for special event (e.g. sidelink BSR/timer controlledbased MAC CE/new uplink MAC CE) and how to monitor downlink controlresource sets when SR is transmitted and not cancelled are discussedabove. The discussion now turns to how to handle new coming eventtriggering SR when there is ongoing SR transmission.

Possible cases for occurring order of different SR triggering conditionsare listed below:

Case A. Uplink data arrival (ongoing); Higher priority uplink dataarrival (new)Case B. Special event (ongoing); Uplink data arrival (new)Case C. Uplink data arrival (ongoing); Special event (new)Case D. Special event (ongoing); Special event (new)Note: The special event can be referred to cases 1, 2, and 3 (e.g.sidelink BSR, etc.) in above discussion.

Applying Method 1 (Multiple SR Resource Sets/Multiple SR Configurationsfor Requesting Resource on Different Numerologies)

In case A, a UE is transmitting SR for uplink data arrival case. Morespecifically, the uplink data arrival means that a regular BSR istriggered due to buffer becoming non-empty or higher priority datacoming. Since SR transmission may not be received, the UE should keeptransmitting SR in its SR transmission opportunities. While UE keepstransmitting SR, higher priority data may arrive and trigger anotherregular BSR. In such condition, the case A will occur.

Assuming the new data arrival will trigger SR based on different SRconfigurations from SR configuration of ongoing SR transmission, thefollowing possible solutions regarding how to handle SR transmission(s)based on the multiple SR configurations in case A are proposed:

Solution 1 (Parallel SR transmissions based on multiple SRconfigurations)—In this solution, the UE can support to transmitmultiple SR transmissions based on different SR configurations. Themultiple SR transmissions may occur on same or different cells (e.g. allon PCell or one on PCell, other on SCell). Hence, the new uplink dataarrival event triggers SR transmission based on a SR configuration,while current SR transmission performed based on another SRconfiguration.

Based on this solution, the network can derive more information from SRtransmissions belonging to the same UE. For example, if ongoing event isfor delay sensitive data and new data arrival is for latency endurabledata, parallel multiple SR transmission based on different SRconfigurations can help network (e.g. gNB) to provide data resource fordelay sensitive for satisfying the need of both new events and currentevent.

Solution 2 (Update SR transmission to reflect highest priority need(either new event or current buffer size)—The UE may or may not supportparallel multiple SR transmissions based on different SR configurations.If the UE does not support, the UE will need to stop current SRtransmission for initiating SR transmission based on a SR configurationdifferent from current used SR configuration.

Depending on whether the new event is triggered for higher prioritydata, the UE will decide whether to switch to use a different SRconfiguration to perform SR transmission. More specifically, the UE willchange to use SR configuration related to new event (e.g. logicalchannel which trigger new event) if the new event is higher prioritydata coming. The UE will not change to use SR configuration related tonew event (e.g. logical channel which trigger new event), if the newevent is for data with priority lower than the priority of the logicalchannel triggered ongoing SR transmission. By this way, the UE cantransmit less SR transmissions and reduce power consumption.

Solution 3 (Keep using ongoing SR configuration instead of initiating SRtransmission based on a different SR configuration for new arrivaldata)—The UE will keep transmitting SR transmission based on currentused SR configuration, regardless whether there is higher priority datacoming.

Solution 4 (Decide whether to change SR configuration based onlatency)—The UE will decide whether to use a SR configuration related tonew event based on latency requirement of data. If the latencyrequirement of data related to new event is tighter than requirement ofany data in the buffer, the UE will initiate SR transmission based on SRconfiguration related to new event. Regarding ongoing SR transmission,the UE may or may not stop current SR transmission even if a new SRtransmission for a different SR configuration is initiated. The latencycould be derived based on QoS of the logical channel to which the databelongs. The latency could be derived based on TTI and/or numerology ofthe logical channel to which the data belongs.

Solution 5 (Use SR configuration related to latest SR triggering eventto perform SR transmission)—The UE will initiate SR transmission basedon SR configuration related to the new event (e.g. higher priority datacoming, retx-BSR timer expiry, etc.).

In case B, a UE is transmitting SR for special event case. Morespecifically, the special event could be referred to cases 1, 2, and 3(e.g. sidelink BSR, timer controlled based MAC CE, or new uplink MAC CE)as discussed above. Since SR transmission may not be received, the UEshould keep transmitting SR in its SR transmission opportunities. Whilethe UE keeps transmitting SR, uplink data may arrive and trigger aregular BSR. In such condition, case B will occur. The differencebetween case B and case C is the triggering order between the specialevent and uplink data arrival event.

Assuming the new coming event (e.g. uplink data arrival or specialevent) will trigger SR based on different SR configurations from SRconfiguration of ongoing SR transmission, possible solutions baseddifferent special event regarding how to handle SR transmission(s) basedon the multiple SR configurations are proposed as follows:

Regular Sidelink BSR Triggers SR

Solution 1 (Parallel SR transmissions based on multiple SRconfigurations)—In this solution, the UE can support to transmitmultiple SR transmissions based on different SR configurations. Themultiple SR transmissions may occur on same or different cells (e.g. allon PCell or one on PCell, other on SCell or any other possiblecombination between multiple SCells and PCell). Hence, the new event(e.g. uplink data arrival) triggers SR transmission based on a SRconfiguration, while current SR transmission performed based on anotherSR configuration.

Based on this solution, the network can derive more information from SRtransmissions belonging to the same UE. For example, the network (e.g.gNB) can discover the occurrence of uplink data arrival and specialevent.

Solution 2 (Update SR transmission to reflect highest priority need(either new event or current buffer size)—The UE may or may not supportparallel multiple SR transmissions based on different SR configurations.If UE does not support, the UE will need to stop current SR transmissionfor initiating SR transmission based on a SR configuration differentfrom current used SR configuration.

Since UE needs to reflect higher priority need in this solution, thepriority between special event and uplink data arrival will need to bedefined clearly. Some possible options are listed below:

1. Follow Logical channel prioritization rule—In the current LCPmechanism, each MAC CE and data will have corresponding priority fordeciding including order and/or deciding what should be included ifthere is not enough resource to accommodate all data and uplink MAC CE.The priority comparison could occur between the uplink data and MAC CE(regular sidelink BSR) related to the special event. Moreover, theuplink data may not belong to any LCG or be configured or indicated asspecial data (e.g. with special indication or threshold in configurationof logical channel the special data belonging to, or duplication data inone leg). Since the uplink data arrival event triggers regular BSR andindirectly triggers SR, the priority comparison could occur between theregular uplink BSR and MAC CE (regular sidelink BSR) related to thespecial event.

Depending on priority comparison result, the SR transmission will beperformed based on a SR configuration related to event with higherpriority. The UE may stop using current SR configuration.

2. Follow network configuration (e.g. threshold, configuration ofspecific logical channel, etc.)—In this option, network (e.g. gNB) canset up the prioritization between new coming event and current event.More specifically, network can set up prioritization based onconfiguring a threshold or sending an indication (in configuration).

For example, the network can provide a threshold related to priority ofsidelink data to decide whether regular sidelink BSR is more importantthan regular uplink BSR. If sidelink BSR is for reporting data withpriority above the threshold, the regular sidelink BSR is moreimportant. Alternatively, it can also be that the regular sidelink BSRis more important if sidelink BSR is for reporting data with prioritybelow the threshold. There could be more than one thresholds (or calledlimitation) for creating a range for prioritization. The priority ofsidelink data could be replaced to priority of uplink logical channel,or QoS flow.

As another example, the network can provide an indication in a(sidelink) logical channel configuration or in a sidelink serviceconfiguration (e.g. V2V, D2D relay, V2X, MBMS, URLLC, full-duplex, etc.)or in MAC CE related configuration. If such indication is included, thepriority could be prioritized.

In one embodiment, if the indication is in a logical channelconfiguration, the regular uplink BSR will be prioritized if the databecoming available for that logical channel. Furthermore, if theindication is in a sidelink service configuration (e.g. V2V, D2D relay,etc.), the sidelink BSR will be prioritized if the data becomingavailable for service. In addition, if the indication is in a MAC CErelated configuration, the MAC CE will be prioritized.

The indication may or may not indicate how much it can be prioritized.If the indication cannot indicate how much it can be prioritized (e.g.prioritized over uplink BSR, or SPS confirmation, or even CCCH SDU), theMAC CE (e.g. sidelink BSR, New uplink MAC CE, or Timer controlled basedMAC CE) will be prioritized over what MAC CE or what data should bepredefined. If the indication indicates how much it can be prioritized,the indication may include sort of index (e.g. LCP rule position, etc.)or value (e.g. priority) or bitmap (e.g. priority bitmap or LCP ruleposition bitmap) for informing the prioritized result.

By this way, UE can transmit less SR transmission and reduce powerconsumption.

Solution 3 (Keep using ongoing SR configuration instead of initiating SRtransmission based on a different SR configuration for new arrivaldata)—The UE will keep transmitting SR transmission based on currentused SR configuration, regardless of what new coming event is. The SRconfiguration used to performing SR transmission may be updated if SRtriggering event related to current SR transmission is cancelled.

Solution 4 (Decide whether to change SR configuration based onlatency)—The UE will decide whether to use a SR configuration related tonew event based on latency requirement of data (e.g. sidelink data). Ifthe latency requirement of data related to new event is tighter thanrequirement of any data in the buffer, the UE will initiate SRtransmission based on SR configuration related to new event. Regardingongoing SR transmission, the UE may or may not stop current SRtransmission even if a new SR transmission for a different SRconfiguration is initiated.

The latency comparison may occur between uplink data and sidelink data.For example, if minimum latency requirement of the sidelink data in thebuffer is associated with 1 ms and minimum latency requirement of theuplink data in the buffer is 4 ms (e.g. eMBB), the sidelink BSR will beprioritized. Alternatively, the comparison occur between MAC CEs.

Moreover, since MAC CE has no latency requirement in LTE, the latencyrequirement for MAC CE may need to be defined and/or to be configuredfor applying this solution. For example, the sidelink BSR will bedefined with a latency requirement based on numerology of sidelinkresource pool or cell for performing sidelink transmission. As anotherexample, the sidelink BSR will be defined with a latency requirementbased on sidelink logical channel (with data) or sidelink QoS flow (withdata).

Solution 5 (Use SR configuration related to latest SR triggering eventto perform SR transmission)—The UE will initiate SR transmission basedon SR configuration related to the new event (e.g. higher priority datacoming or retx-BSR timer expiry, or special event, etc.). For example,assume the sidelink BSR is triggered when SR for uplink BSR istransmitted. The SR configuration used for current SR transmission willbe changed to SR configuration related to sidelink BSR.

Solution 6 (Always prioritize uplink data need over the special event(e.g. sidelink BSR))—If new coming event is regular sidelink BSR andcurrent SR transmission reflects uplink data need, the UE will keepusing the current SR configuration. On the contrary, if new coming eventis for uplink data need and current SR transmission is for regularsidelink BSR, the UE will change the current SR configuration to adifferent SR configuration related to the new coming event.

Timer Controlled Based MAC CE Triggers SR

Solution 1 (Parallel SR transmissions based on multiple SRconfigurations)—In this solution, the UE can support to transmitmultiple SR transmissions based on different SR configurations. Themultiple SR transmissions may occur on same or different cells (e.g. allon PCell or one on PCell, other on SCell or any other possiblecombination between multiple SCells and PCell). Hence, the new event(e.g. uplink data arrival, special event) triggers SR transmission basedon a SR configuration, while current SR transmission performed based onanother SR configuration.

Based on this solution, the network can derive more information from SRtransmissions belonging to the same UE. For example, the network (e.g.gNB) can discover the occurrence of uplink data arrival and specialevent.

Solution 2 (Update SR transmission to reflect highest priority need(either new event or current buffer size))—The UE may or may not supportparallel multiple SR transmissions based on different SR configurations.If UE does not support, the UE will need to stop current SR transmissionfor initiating SR transmission based on a SR configuration differentfrom current used SR configuration.

Since the UE needs to reflect higher priority need in this solution, thepriority between special event and uplink data arrival will need to bedefined clearly. Possible options are listed below:

1. Follow Logical channel prioritization rule—In the current LCPmechanism, each MAC CE and data will have corresponding priority fordeciding including order and/or deciding what should be included ifthere is not enough resources to accommodate all data and uplink MAC CE.The priority comparison could occur between the uplink data (e.g.highest priority data in the buffer) and MAC CE (Timer controlled basedMAC CE) related to the special event. Moreover, the uplink data may notbelong to any LCG or be configured or indicated as special data (e.g.with special indication or threshold in configuration of logical channelthe special data belonging to, or duplication data in one leg). Sincethe uplink data arrival event triggers regular BSR and indirectlytriggers SR, the priority comparison could occur between the regularuplink BSR and MAC CE (Timer controlled based MAC CE) related to thespecial event.

Depending on priority comparison result, SR transmission will beperformed based on a SR configuration related to event with higherpriority. The UE may stop using current SR configuration.

2. Follow network configuration (e.g. threshold, configuration ofspecific logical channel, etc.)—In this candidate, network (e.g. gNB)can set up the prioritization between new coming event and currentevent. More specifically, network can set up prioritization based onconfiguring a threshold or sending an indication (in configuration).

For example, network can provide a threshold related to priority ofuplink logical channel to decide whether Timer controlled based MAC CEis more important than regular uplink BSR. If BSR is for reporting databelonging to a logical channel with priority above the threshold, theregular uplink BSR is more important. Alternatively, the regular uplinkBSR could be more important if BSR is for reporting data belonging to alogical channel with priority below the threshold. There could be morethan one thresholds (or called limitation) for creating a range forprioritization. The priority of uplink logical channel could be replacedto QoS flow.

As another example, the network can provide an indication in a logicalchannel configuration or in a service configuration (e.g. V2X, relay,MBMS, URLLC, full-duplex, etc.) or in MAC CE related configuration. Ifsuch indication is included, the priority could be prioritized.

In one embodiment, if the indication is in a logical channelconfiguration, the regular uplink BSR will be prioritized if the databecoming available for that logical channel. Furthermore, if theindication is in a service configuration (e.g. V2V, D2D relay, etc.),the BSR will be prioritized if the data becoming available for service.In addition, if the indication is in a MAC CE related configuration, theMAC CE will be prioritized.

The indication may or may not indicate how much it can be prioritized.If the indication cannot indicate how much it can be prioritized thenthe MAC CE (e.g. sidelink BSR, New uplink MAC CE, or Timer controlledbased MAC CE) will be prioritized over what MAC CE or what data shouldbe predefined. If the indication indicates how much it can beprioritized, the indication may include sort of index (e.g. LCP ruleposition, etc.) or value (e.g. priority) or bitmap (e.g. priority bitmapor LCP rule position bitmap) for informing the prioritized result. Bythis way, UE can transmit less SR transmission and reduce powerconsumption.

Solution 3 (Keep using ongoing SR configuration instead of initiating SRtransmission based on a different SR configuration for new arrivaldata)—The UE will keep transmitting SR transmission based on currentused SR configuration, regardless of what new coming event is. The SRconfiguration used to performing SR transmission may be updated if SRtriggering event related to current SR transmission is cancelled.

Solution 4 (Decide whether to change SR configuration based onlatency)—The UE will decide whether to use a SR configuration related tonew event based on latency requirement of new coming event (e.g. regularBSR for a logical channel or timer controlled based MAC CE). If thelatency requirement related to new event is tighter than latencyrequirement of any other current SR triggering event(s), the UE willinitiate SR transmission based on SR configuration related to new event.Regarding ongoing SR transmission, the UE may or may not stop current SRtransmission even if a new SR transmission for a different SRconfiguration is initiated.

Since MAC CE has no latency requirement in LTE, the latency requirementfor MAC CE may need to be defined and/or to be configured for applyingthis solution. One possible way is to associate the timer controlledbased MAC CE with certain TTI duration and/or certain numerology (inrelated configuration). The associated TTI duration and/or numerologymay also be used for timer counting.

Solution 5 (Use SR configuration related to latest SR triggering eventto perform SR transmission)—The UE will initiate SR transmission basedon SR configuration related to the new event (e.g. higher priority datacoming or retx-BSR timer expiry, or special event . . . ). For example,assuming the Timer controlled based MAC CE is triggered when SR foruplink BSR is transmitted, the SR configuration used for current SRtransmission will be changed to SR configuration related to Timercontrolled based MAC CE.

Solution 6 (Always prioritize uplink data need over the special event(e.g. Timer controlled based MAC CE))—If the new coming event is Timercontrolled based MAC CE and current SR transmission reflects uplink dataneed, the UE will keep using the current SR configuration. On thecontrary, if new coming event is for uplink data need and current SRtransmission is for Timer controlled based MAC CE, the UE will changethe current SR configuration to a different SR configuration related tothe new coming event.

Solution 7 (Define prioritization between each special event and uplinkdata arrival case by case)—It is possible to define relation betweeneach potential uplink MAC CE(s) and uplink BSR and any other MAC CEwhich can trigger SR transmission (e.g. sidelink BSR, timer controlledbased MAC CE). In this solution, for example, a timer controlled basedMAC CE (e.g. beam related MAC CE) could be defined to always prioritizeover uplink data arrival. Moreover, another timer controlled based (e.g.(sidelink) PHR) could be defined to have lower priority compared withuplink data arrival (e.g. regular BSR). Based on defined result, the UEmay always prioritize a special event (e.g. a specific MAC CE which isnot BSR) over uplink data arrival case (e.g. regular BSR). In addition,the UE may also always prioritize uplink data arrival case (e.g. regularBSR) over another special event (e.g. a specific MAC CE which is notBSR). The UE may also always prioritize a special event over anotherspecial event based on defined result.

New Uplink MAC CE Triggers SR (Case 3 in Above Discussion)

Solution 1 (Parallel SR transmissions based on multiple SRconfigurations)—In this solution, the UE can support to transmitmultiple SR transmissions based on different SR configurations. Themultiple SR transmissions may occur on same or different cells (e.g. allon PCell or one on PCell, other on SCell or any other possiblecombination between multiple SCells and PCell). Hence, the new event(e.g. uplink data arrival, special event) triggers SR transmission basedon a SR configuration, while current SR transmission performed based onanother SR configuration.

Based on this solution, the network can derive more information from SRtransmissions belonging to the same UE. For example, the network (e.g.gNB) can discover the occurrence of uplink data arrival and specialevent.

Solution 2 (Update SR transmission to reflect highest priority need(either new event or current buffer size))—The UE may or may not supportparallel multiple SR transmissions based on different SR configurations.If UE does not support, the UE will need to stop current SR transmissionfor initiating SR transmission based on a SR configuration differentfrom current used SR configuration.

Since UE needs to reflect higher priority need in this solution, thepriority between special event and uplink data arrival will need to bedefined clearly. Possible options are listed below:

1. Follow Logical channel prioritization rule—In the current LCPmechanism, each MAC CE and data will have corresponding priority fordeciding including order and/or deciding what should be included ifthere is not enough resource to accommodate all data and uplink MAC CE.The priority comparison could occur between the uplink data (e.g.highest priority data in the buffer) and MAC CE New uplink MAC CE)related to the special event. Moreover, the uplink data may not belongto any LCG or be configured or indicated as special data (e.g. withspecial indication or threshold in configuration of logical channel thespecial data belonging to, or duplication data in one leg). Since theuplink data arrival event triggers regular BSR and indirectly triggersSR, the priority comparison could occur between the regular uplink BSRand MAC CE (New uplink MAC CE) related to the special event.

Depending on priority comparison result, SR transmission will beperformed based on a SR configuration related to event with higherpriority. The UE may stop using current SR configuration.

2. Follow network configuration (e.g. threshold, configuration ofspecific logical channel, etc.)—In this option, the network (e.g. gNB)can set up the prioritization between new coming event and currentevent. More specifically, the network can set up prioritization based onconfiguring a threshold or sending an indication (in configuration).

For example, the network can provide a threshold related to priority ofuplink logical channel to decide whether New uplink MAC CE is moreimportant than regular uplink BSR. If BSR is for reporting databelonging to a logical channel with priority above the threshold, theregular uplink BSR is more important. Alternatively, the regular uplinkBSR could be more important if BSR is for reporting data belonging to alogical channel with priority below the threshold. There could be morethan one thresholds (or called limitation) for creating a range forprioritization. The priority of uplink logical channel could be replacedto QoS flow.

As another example, the network can provide an indication in a logicalchannel configuration or in a service configuration (e.g. V2X, relay,MBMS, URLLC, full-duplex, etc.) or in New uplink MAC CE relatedconfiguration. If such indication is included, the priority could beprioritized.

In one embodiment, if the indication is in a logical channelconfiguration, the regular uplink BSR will be prioritized if the databecoming available for that logical channel. Furthermore, if theindication is in a service configuration (e.g. V2V, D2D relay, etc.),the BSR will be prioritized if the data becoming available for service.In addition, if the indication is in a New uplink MAC CE relatedconfiguration, the New uplink MAC CE will be prioritized.

The indication may or may not indicate how much it can be prioritized.If the indication cannot indicate how much it can be prioritized, theMAC CE (e.g. sidelink BSR/New uplink MAC CE/Timer controlled based MACCE) will be prioritized over what MAC CE or what data should bepredefined. If the indication indicates how much it can be prioritized,the indication may include sort of index (e.g. LCP rule position, etc.)or value (e.g. priority) or bitmap (e.g. priority bitmap or LCP ruleposition bitmap) for informing the prioritized result. By this way, theUE can transmit less SR transmission and reduce power consumption.

Solution 3 (Keep using ongoing SR configuration instead of initiating SRtransmission based on a different SR configuration for new arrivaldata)—The UE will keep transmitting SR transmission based on currentused SR configuration, regardless of what new coming event is. The SRconfiguration used to performing SR transmission may be updated if SRtriggering event related to current SR transmission is cancelled.

Solution 4 (Decide whether to change SR configuration based onlatency)—The UE will decide whether to use a SR configuration related tonew event based on latency requirement of new coming event (e.g. regularBSR for a logical channel or Potential new MAC CE). If the latencyrequirement related to new event is tighter than latency requirement ofany other current SR triggering event(s), the UE will initiate SRtransmission based on SR configuration related to new event. Regardingongoing SR transmission, the UE may or may not stop current SRtransmission even if a new SR transmission for a different SRconfiguration is initiated.

Since MAC CE has no latency requirement in LTE, the latency requirementfor MAC CE may need to be defined and/or to be configured for applyingthis solution. Since MAC CE has no latency requirement in LTE, thelatency requirement for MAC CE may need to be defined and/or to beconfigured for applying this solution. One possible way is to associatethe potential new MAC CE with certain TTI duration and/or certainnumerology (in related configuration). The associated TTI durationand/or numerology may also be used for timer counting.

Solution 5 (Use SR configuration related to latest SR triggering eventto perform SR transmission)—The UE will initiate SR transmission basedon SR configuration related to the new event (e.g. higher priority datacoming or retx-BSR timer expiry, or special event . . . ). For example,assume the New uplink MAC CE is triggered when SR for uplink BSR istransmitted. The SR configuration used for current SR transmission willbe changed to SR configuration related to New uplink MAC CE.

Solution 6 (Always prioritize uplink data need over the special event(e.g. New uplink MAC CE))—If new coming event is Timer controlled basedMAC CE and current SR transmission reflects uplink data need, the UEwill keep using the current SR configuration. On the contrary, if newcoming event is for uplink data need and current SR transmission is forNew uplink MAC CE, the UE will change the current SR configuration to adifferent SR configuration related to the new coming event.

Solution 7 (Define prioritization between each special event and uplinkdata arrival case by case)—Relation between each potential uplink MACCE(s) and uplink BSR and any other MAC CE which can trigger SRtransmission (e.g. sidelink BSR, timer controlled based MAC CE) could bedefined. In this solution, for example, a potential uplink MAC CE (e.g.beam related MAC CE) could be defined to be always prioritized overuplink data arrival. In addition, another potential uplink MAC CE (e.g.(sidelink) PHR) has lower priority compared with uplink data arrival(e.g. regular BSR) could be defined. Based on defined result, the UE mayalways prioritize a special event (e.g. a specific MAC CE which is notBSR) over uplink data arrival case (e.g. regular BSR). Furthermore, theUE may also always prioritize uplink data arrival case (e.g. regularBSR) over another special event (e.g. a specific MAC CE which is notBSR). The UE may also always prioritize a special event over anotherspecial event based on defined result.

In case D, a UE is transmitting SR for special event case. Morespecifically, the special event could be referred to cases 1, 2, and 3(e.g. sidelink BSR/timer controlled based MAC CE/new uplink MAC CE) asdiscussed above. Since SR transmission may not be received, the UEshould keep transmitting SR in its SR transmission opportunities. WhileUE keeps transmitting SR, another special event may be triggered andindirectly trigger SR. In such condition, case D will occur.

Solution 1 (Parallel SR transmissions based on multiple SRconfigurations)—In this solution, the UE can support to transmitmultiple SR transmissions based on different SR configurations. Themultiple SR transmissions may occur on same or different cells (e.g. allon PCell or one on PCell, other on SCell or any other possiblecombination between multiple SCells and PCell). Hence, the new event(e.g. special event) triggers SR transmission based on a SRconfiguration, while current SR transmission performed based on anotherSR configuration (for previous SR triggering event).

Based on this solution, the network can derive more information from SRtransmissions belonging to the same UE. For example, the network (e.g.gNB) can discover the occurrence of different special events.

Solution 2 (Update SR transmission to reflect highest priority need(either new event or current buffer size)—The UE may or may not supportparallel multiple SR transmissions based on different SR configurations.If UE does not support, the UE will need to stop current SR transmissionfor initiating SR transmission based on a SR configuration differentfrom current used SR configuration.

Since the UE needs to reflect higher priority need in this solution, thepriority between the special events will need to be defined clearly.Possible candidates are listed below:

1. Follow Logical channel prioritization rule—In the current LCPmechanism, each uplink MAC CE and data will have corresponding priorityfor deciding including order and/or deciding what should be included ifno enough resource can accommodate all data and uplink MAC CE. Thepriority comparison could occur between MAC CEs related to differentspecial events.

Depending on priority comparison result, SR transmission will beperformed based on a SR configuration related to event with higherpriority. The UE may stop using current SR configuration to perform SRtransmission.

2. Follow network configuration (e.g. threshold, configuration ofspecific logical channel, etc.)—In this candidate, the network (e.g.gNB) can set up the prioritization between new coming event and currentevent. More specifically, the network can set up prioritization based onconfiguring a threshold or sending an indication (in configuration).

For example, the network can provide a threshold related to priority ofsidelink logical channel to decide whether certain special event(s) ismore important than regular sidelink BSR. If sidelink BSR is forreporting data belonging to a logical channel with priority above thethreshold, the regular sidelink BSR is more important. Alternatively,the regular sidelink BSR could be more important if sidelink BSR is forreporting sidelink data belonging to a logical channel with prioritybelow the threshold. There could be more than one thresholds (or calledlimitation) for creating a range for prioritization.

As another example, network can provide an indication in a serviceconfiguration (e.g. V2V, V2X, relay, MBMS, URLLC, full-duplex, etc.) orin special event related configuration (e.g. beam-forming configuration,SPS configuration, grant free configuration, Packet duplicationconfiguration). If such indication is included, the priority of relatedMAC CE could be prioritized.

In one embodiment, if the indication is in a service configuration (e.g.V2V, D2D relay, . . . ), the BSR will be prioritized if the databecoming available for service. Furthermore, if the indication is in aspecial event related configuration, the corresponding MAC CE will beprioritized.

The indication may or may not indicate how much it can be prioritized.If the indication cannot indicate how much it can be prioritized, theMAC CE (e.g. sidelink BSR/New uplink MAC CE/Timer controlled based MACCE) will be prioritized over what MAC CE or what data should bepredefined. If the indication indicates how much it can be prioritized,the indication may include sort of index (e.g. LCP rule position, etc.)or value (e.g. priority) or bitmap (e.g. priority bitmap or LCP ruleposition bitmap) for informing the prioritized result. By this way, theUE can transmit less SR transmission and reduce power consumption.

Solution 3 (Keep using ongoing SR configuration instead of initiating SRtransmission based on a different SR configuration for new arrivaldata)—The UE will keep transmitting SR transmission based on currentused SR configuration, regardless of what new coming event is. The SRconfiguration used to performing SR transmission may be updated if SRtriggering event related to current SR transmission is cancelled.

Solution 4 (Decide whether to change SR configuration based onlatency)—The UE will decide whether to use a SR configuration related tonew event based on latency requirement of new coming special event. Ifthe latency requirement related to new event is tighter than latencyrequirement of any other current SR triggering event(s), the UE willinitiate SR transmission based on SR configuration related to new event.Regarding ongoing SR transmission, the UE may or may not stop current SRtransmission even if a new SR transmission for a different SRconfiguration is initiated.

Since MAC CE has no latency requirement in LTE, the latency requirementfor MAC CE may need to be defined and/or to be configured for applyingthis solution.

Solution 5 (Use SR configuration related to latest SR triggering eventto perform SR transmission)—The UE will initiate SR transmission basedon SR configuration related to the new event (e.g. retx-BSR timerexpiry, or special event). For example, assuming the New uplink MAC CEis triggered when SR for sidelink BSR is transmitted, the SRconfiguration used for current SR transmission will be changed to SRconfiguration related to New uplink MAC CE.

Solution 6 (Define prioritization between each special event case bycase)—Relation between each potential uplink MAC CE(s) and uplink BSRand any other MAC CE which can trigger SR transmission (e.g. sidelinkBSR, timer controlled based MAC CE) could be defined. In this solution,for example, a potential uplink MAC CE (e.g. beam related MAC CE) couldbe defined to be always prioritized over sidelink BSR. Moreover, anotherpotential uplink MAC CE (e.g. (sidelink) PHR) has lower prioritycompared with a timer controlled based MAC CE could be defined. Based ondefined result, the UE may always prioritize a special event (e.g. aspecific MAC CE which is not BSR) over another special event.

How SR configuration is related to or associated with new event can bereferred to the above discussion about how to trigger SR for specialevent. Furthermore, the relation between SR configuration and uplinkdata arrival is between logical channel information and SRconfiguration. The logical channel information could be LCID, TTIduration limitation, numerology, or cell belonging.

FIG. 31 is an exemplary embodiment for the parallel multiple SRtransmissions based on different SR configurations. The UE is performingSR transmission based on SR configuration 1. When a new event is comingand the new event is related to SR configuration 2, UE will also performSR transmission based SR configuration 2, while SR transmissions basedon SR configuration 1 will not be stopped and/or cancelled.

FIG. 32 is an exemplary embodiment for following LCP rule to prioritize.In particular, FIG. 32 illustrates following LCP rule to decide performSR transmission based on which SR configuration in multiple SRconfigurations. As shown in FIG. 32, the UE is transmitting SR based onSR configuration related to Sidelink. More specifically, SRconfiguration is related to sidelink BSR. However, when a regular uplinkBSR is trigged by uplink data arrival and SR configuration 2 is relatedto the regular uplink BSR for reflecting the need of uplink data inbuffer (e.g. logical channel which indirectly trigger SR), the SRtransmission based on SR configuration 1 will be stopped becausesidelink BSR has lower priority than uplink BSR. The UE will start toperform SR transmission based on SR configuration 2.

FIG. 33 is an exemplary embodiment for following the latest event. Inparticular, FIG. 33 illustrates parallel multiple SR transmissions basedon different SR configurations. In this example, the first new event isassociated with SR configuration 2. Hence, the UE will change to performSR transmission based on SR configuration 2 and stop SR transmissionbased on SR configuration 1 based on the solution. When a second newevent related to SR configuration 1 occurs, the UE will change back touse SR configuration 1 to perform SR transmissions.

FIG. 34 is an exemplary embodiment for always following uplink dataneed. When a UE is transmitting SR for new uplink MAC CE which isrelated to SR configuration 2, an uplink data arrival event occurs. TheUE will change to use SR configuration 2 to perform SR transmission dueto uplink data arrival event related to SR configuration 2. The uplinkdata arrival event is related to SR configuration 2 because theTTI/numerology type need of the uplink data should be distinguished bySR configuration 2.

FIG. 35 is a flow chart 3500 according to one exemplary embodiment of aUE, wherein the UE is allocated with multiple SR configurations by anetwork node. In step 3505, the UE triggers a MAC control element if atimer expires. In step 3510, the UE triggers a SR for the MAC controlelement. In step 3515, the UE transmits the SR based on a first SRconfiguration of the multiple SR configurations, wherein the first SRconfiguration is associated with a highest priority logical channelhaving data available for transmission when the MAC control element istriggered.

In one embodiment, the timer could be a retxBSR-Timer. The MAC controlelement could be a BSR. The first SR configuration could be associatedwith the highest priority logical channel based on an identity of thehighest priority logical channel.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UEwherein the UE is allocated with multiple SR configurations by a networknode, the device 300 includes a program code 312 stored in the memory310. The CPU 308 could execute program code 312 to enable the UE (i) totrigger a MAC control element if a timer expires, (ii) to trigger a SRfor the MAC control element, and (iii) to transmit the SR based on afirst SR configuration of the multiple SR configurations, wherein thefirst SR configuration is associated with a highest priority logicalchannel having data available for transmission when the MAC controlelement is triggered. Furthermore, the CPU 308 can execute the programcode 312 to perform all of the above-described actions and steps orothers described herein.

FIG. 36 is a flow chart 3600 according to one exemplary embodiment of aUE. In step 3605, the UE receives multiple SR configurations from anetwork node. In step 3610, the UE triggering a first MAC controlelement. In step 3615, the UE triggers a first SR for the first MACcontrol element. In step 3620, the UE transmits a first SR to thenetwork node according to a first SR configuration of the multiple SRconfigurations, wherein the first SR configuration is selected based ona characteristic of the first SR configuration.

In one embodiment, the characteristic could be the first SRconfiguration has the closest SR transmission opportunity after thefirst MAC control element is triggered. The first MAC control elementcould be a sidelink BSR. The first MAC control element could betriggered due to a timer expiry.

In one embodiment, the UE could trigger a second MAC control element foran uplink data of a first logical channel. And the UE could trigger asecond SR for the second MAC control element. Furthermore, the UE couldtransmit the second SR to the network node according to a second SRconfiguration of the multiple SR configurations, wherein the second SRconfiguration is selected based on an association between the firstlogical channel and the second SR configuration.

In one embodiment, the UE could perform the second SR transmissionaccording to the second SR configuration without suspending or stoppingperforming a third SR transmission according to the first SRconfiguration. Alternatively, the UE could stop performing a third SRtransmission according to the first SR configuration when the UEtriggers the second MAC control element.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to receivemultiple SR configurations from a network node, (ii) to trigger a firstMAC control element, (iii) to trigger a first SR for the first MACcontrol element, and (iv) to transmit the first SR to the network nodeaccording to a first SR configuration of the multiple SR configurations,wherein the first SR configuration is selected based on a characteristicof the first SR configuration. Furthermore, the CPU 308 can execute theprogram code 312 to perform all of the above-described actions and stepsor others described herein.

FIG. 37 is a flow chart 3700 according to one exemplary embodiment of aUE, wherein the UE is allocated with multiple SR configurations by anetwork node and there is an association between a MAC control elementand a first SR configuration in the multiple SR configurations. In step3705, the UE triggers the MAC control element. In step 3710, the UEtransmits a SR based on the first SR configuration.

In one embodiment, the association could be established by linking theMAC control element to a TTI (Transmission Time Interval) lengthinformation (e.g. Maximum TTI threshold, etc.). The first SRconfiguration could be associated with the TTI length information.

Alternatively, the association could be established by linking the MACcontrol element to a numerology information. The first SR configurationcould be associated with the numerology information.

Furthermore, the association could be established by linking the MACcontrol element to one or multiple logical channel identity. The firstSR configuration could be associated with the logical channel identity.

In addition, the association could be established by linking the MACcontrol element to one or multiple logical channel group(s). The firstSR configuration is associated with the logical channel group. Also, thefirst SR configuration could include information related to the MACcontrol element (e.g. identity of MAC CE, corresponding service identity(e.g. sidelink, MBMS, V2X), etc.).

The association could also be established by including informationrelated to the MAC control element in the first SR configuration.

The association could be established by including information (e.g.index, identity, etc.) of the first SR configuration into aconfiguration related to the MAC control element. The configurationcould be a service configuration (e.g. sidelink configuration, V2Xconfiguration, MBMS configuration, etc.). The configuration could be aMAC configuration.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to triggerthe MAC control element, and (ii) to transmit a SR based on the first SRconfiguration. Furthermore, the CPU 308 can execute the program code 312to perform all of the above-described actions and steps or othersdescribed herein.

FIG. 38 is a flow chart 3800 according to one exemplary embodiment of aUE, wherein the UE is allocated with multiple SR configurations by anetwork node with predefined rule for selecting SR configuration. Instep 3805, the UE receives multiple SR configurations from a networknode. In step 3810, the UE triggers a MAC control element. In step 3815,the UE transmits a SR to the network node according to one SRconfiguration of the multiple SR configurations, wherein the SRconfiguration is selected based on a characteristic of the SRconfiguration.

In one embodiment, the characteristic could be SR configuration used forrequesting resource on default numerology or access numerology. Thecharacteristic could also be SR configuration allocated on defaultnumerology or access numerology. Furthermore, the characteristic couldbe SR configuration with densest SR transmission opportunities comparingwith other SR configuration(s). In addition, the characteristic could beSR configuration has the closest SR transmission opportunity after thetrigger timing of the MAC control element. The characteristic could alsobe SR configuration is used for requesting shortest TTI and/or largestnumerology resource which the UE can use. Furthermore, thecharacteristic could be SR configuration dedicated for requestingtransmission resource for the MAC control element.

In one embodiment, the UE does not have multiple connectivities.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UEwherein the UE is allocated with multiple SR configurations by a networknode with predefined rule for selecting SR configuration, the device 300includes a program code 312 stored in the memory 310. The CPU 308 couldexecute program code 312 to enable the UE (i) to receive multiple SRconfigurations from a network node, (ii) to trigger a MAC controlelement, and (iii) to transmit a SR to the network node according to oneSR configuration of the multiple SR configurations, wherein the SRconfiguration is selected based on a characteristic of the SRconfiguration. Furthermore, the CPU 308 can execute the program code 312to perform all of the above-described actions and steps or othersdescribed herein.

FIG. 39 is a flow chart 3900 according to one exemplary embodiment of aUE, wherein the UE is allocated with one SR configuration by a networknode that configures multiple bits SR setting for control element andwherein there is a mapping between a MAC control element and a value orvalues of one or multiple fields in a SR transmitted according to the SRconfiguration. In step 3905, the UE triggers the MAC control element. Instep 3910, the UE transmits the SR according to the SR configuration tothe network node, wherein the one or multiple fields of the SR is/areset to the value/values mapped to the MAC control element.

In one embodiment, the mapping could be established by linking the MACcontrol element to a TTI length information (e.g. Maximum TTI threshold,etc.). The value or values are associated with the TTI lengthinformation.

Alternatively, the mapping could be established by linking the MACcontrol element to a numerology information (e.g. one or multiplenumerology index, numerology index bitmap, etc.). The value or valuesare associated with the numerology information.

The mapping could also established by linking the MAC control element toone or multiple logical channel identity. The value or values areassociated with the logical channel identity.

Furthermore, the mapping could be established by linking the MAC controlelement to one or multiple logical channel group(s). The value or valuesare associated with the logical channel group.

In addition, the mapping could be established by directly mappinginformation related to the MAC control element (e.g. identity of MAC CE,corresponding service identity (e.g. sidelink, MBMS, V2X), etc.) to thevalue or values in the SR configuration.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UEwherein the UE is allocated with one SR configuration by a network nodethat configures multiple bits SR setting for control element and whereinthere is a mapping between a MAC control element and a value or valuesof one or multiple fields in a SR transmitted according to the SRconfiguration, the device 300 includes a program code 312 stored in thememory 310. The CPU 308 could execute program code 312 to enable the UE(i) to trigger the MAC control element, and (ii) to transmit the SRaccording to the SR configuration to the network node, wherein the oneor multiple fields of the SR is set to the value or values mapped to theMAC control element. Furthermore, the CPU 308 can execute the programcode 312 to perform all of the above-described actions and steps orothers described herein.

FIG. 40 is a flow chart 4000 according to one exemplary embodiment of aUE with predefined multiple bits SR setting for control element. In step4005, the UE receives a SR configuration from a network node, wherein aSR transmission based on the SR configuration includes a first field forthe network node to derive TTI length and/or numerology of uplinkresource demand. In step 4010, the UE transmits a first SR to thenetwork node if the first SR is not triggered by uplink data arrival,wherein the first field in the first SR is set to a first value. In step4015, the UE transmits a second SR to the network node if the second SRis triggered by uplink data arrival, wherein the first field in thesecond SR is set based on numerology and/or TTI need of the uplink dataarrival.

In one embodiment, the first value could be a specific value used toindicate there is at least a MAC control element pending in the UE. Thefirst value could also be a specific value used to indicate the MACcontrol element is triggered. For example, if there are 3 bits in thefirst field, ‘000’˜‘011’ could be used for uplink data arrival cases,‘111’ could be the specific value used to indicate the MAC controlelement, and ‘100’˜‘110’ could be used for other cases or reserved forfuture uses.

In one embodiment, the first value could indicate uplink resource demandon default numerology, initial access numerology, uplink resource demandfor specific range of TTI length, uplink resource demand for a LCG, oruplink resource demand for a logical channel.

In one embodiment, the UE has no data available for transmission in DRBor SRB when triggering the MAC control element.

In one embodiment, the MAC control element could be a Sidelink BSR, acontrol element triggered by a timer, a control element for reportingbeam related information, a control element for reporting a trafficpattern change, or a control element for confirming a command from thenetwork.

In one embodiment, the MAC control element may not be related to logicalchannel.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UEwith predefined multiple bits SR setting for control element, the device300 includes a program code 312 stored in the memory 310. The CPU 308could execute program code 312 to enable the UE (i) to receive a SRconfiguration from a network node, wherein a SR transmission based onthe SR configuration includes a first field for the network node toderive TTI length and/or numerology of uplink resource demand, (ii) totransmit a first SR to the network node if the first SR is not triggeredby uplink data arrival, wherein the first field in the first SR is setto a first value, and (iii) to transmit a second SR to the network nodeif the second SR is triggered by uplink data arrival, wherein the firstfield in the second SR is set based on numerology and/or TTI need of theuplink data arrival. Furthermore, the CPU 308 can execute the programcode 312 to perform all of the above-described actions and steps orothers described herein.

FIG. 41 is a flow chart 4100 according to one exemplary embodiment of aUE, wherein the UE is configured with multiple downlink controlchannels. In step 4105, the UE transmits a scheduling request triggeredby a first condition to a network node, wherein the first condition isdifferent from a condition of a regular BSR triggered by uplink dataarrival. In step 4110, the UE monitors a first set of the multipledownlink control channels.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,wherein the UE is configured with multiple downlink control channels,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to transmita scheduling request triggered by a first condition to a network node,wherein the first condition is different from a condition of a regularBSR triggered by uplink data arrival, and (ii) to monitor a first set ofthe multiple downlink control channels. Furthermore, the CPU 308 canexecute the program code 312 to perform all of the above-describedactions and steps or others described herein.

FIG. 42 is a flow chart 4200 according to one exemplary embodiment of anetwork node, wherein a UE is configured with multiple downlink controlchannels by the network node. In step 4205, the network node receives ascheduling request triggered by a first condition from the UE, whereinthe first condition is different from a condition of a regular BSRtriggered by uplink data arrival. In step 4210, the network nodeprovides uplink resources to the UE via a first set of the multipledownlink control channels.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of anetwork node wherein a UE is configured with multiple downlink controlchannels by the network node, the device 300 includes a program code 312stored in the memory 310. The CPU 308 could execute program code 312 toenable the network node (i) to receive a scheduling request triggered bya first condition from the UE, wherein the first condition is differentfrom a condition of a regular BSR triggered by uplink data arrival, and(ii) to provide uplink resources to the UE via a first set of themultiple downlink control channels. Furthermore, the CPU 308 can executethe program code 312 to perform all of the above-described actions andsteps or others described herein.

In the context of the embodiments shown in FIGS. 41-42 and described inthe text above, in one embodiment, the first condition could be aregular sidelink BSR is triggered, an uplink control element (exceptBSR) is triggered, an uplink control element triggered by a timerexpiry, or an uplink control element triggered by a counter value overthreshold.

In one embodiment, the UE could decide the first set based on a firstrule. The first rule could be selecting control channel(s) associatedwith the first condition, or selecting specific control channel(s)regardless of numerology and/or TTI information carried by thetransmission of the scheduling request.

In one embodiment, the UE could monitor a second set of the multipledownlink control channels if the scheduling request is triggered by asecond condition different from the first condition, wherein the secondset is different from the first set. The UE could also decide the secondset based on a second rule. In one embodiment, the second rule could beselecting control channel(s) associated with the second condition,selecting specific control channel(s) regardless of numerology and/orTTI information carried by the transmission of the scheduling request,selecting all of the multiple control channel(s), or selecting controlchannel(s) based on numerology and/or TTI information carried by thetransmission of the scheduling request.

In one embodiment, the second condition could be a regular sidelink BSRis triggered, an uplink control element (except BSR) is triggered, anuplink control element triggered by a timer expiry, an uplink controlelement triggered by a counter value over threshold, or a regular BSRtriggered by uplink data arrival.

FIG. 43 is a flow chart 4300 according to one exemplary embodiment of aUE, wherein the UE is configured with multiple downlink controlchannels. In step 4305, the UE transmits a scheduling request to anetwork node. In step 4310, the UE monitors a first set of the multipledownlink control channels based on a first rule, if the schedulingrequest is triggered for uplink data arrival. In step 4315, the UEmonitors a second set of the multiple downlink control channels based ona second rule if the scheduling request is triggered for a conditiondifferent from uplink data arrival, wherein the first set is differentfrom the second set.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UE,wherein the UE is configured with multiple downlink control channels,the device 300 includes a program code 312 stored in the memory 310. TheCPU 308 could execute program code 312 to enable the UE (i) to transmita scheduling request to a network node, (ii) to monitor a first set ofthe multiple downlink control channels based on a first rule, if thescheduling request is triggered for uplink data arrival, and (iii) tomonitors a second set of the multiple downlink control channels based ona second rule if the scheduling request is triggered for a conditiondifferent from uplink data arrival, wherein the first set is differentfrom the second set. Furthermore, the CPU 308 can execute the programcode 312 to perform all of the above-described actions and steps orothers described herein.

FIG. 44 is a flow chart 4400 according to one exemplary embodiment of anetwork node, wherein the network node configures a UE with multipledownlink control channels. In step 4405, the network node receiving ascheduling request from the UE. In step 4410, the network node providesuplink resources to the UE via a first set of the multiple downlinkcontrol channels based on a first rule, if the scheduling request istriggered for uplink data arrival. In step 4415, the network nodeprovides uplink resources to the UE via a second set of the multipledownlink control channels based on a second rule if the schedulingrequest is triggered for a condition different from uplink data arrival,wherein the first set is different from the second set.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of anetwork node wherein the network node configures a UE with multipledownlink control channels, the device 300 includes a program code 312stored in the memory 310. The CPU 308 could execute program code 312 toenable the network node (i) to receive a scheduling request from the UE,(ii) to provide uplink resources to the UE via a first set of themultiple downlink control channels based on a first rule, if thescheduling request is triggered for uplink data arrival, and (iii) toprovide uplink resources to the UE via a second set of the multipledownlink control channels based on a second rule if the schedulingrequest is triggered for a condition different from uplink data arrival,wherein the first set is different from the second set. Furthermore, theCPU 308 can execute the program code 312 to perform all of theabove-described actions and steps or others described herein.

In the context of the embodiments shown in FIGS. 43-44 and described inthe text above, in one embodiment, the first rule could be selecting allof the multiple control channel(s) as the first set or selecting controlchannel(s) related to numerology and/or TTI information carried by thetransmission of the scheduling request as the first set.

In one embodiment, the second rule could be selecting all of themultiple control channel(s) as the first set, selecting controlchannel(s) related to numerology and/or TTI information carried by thetransmission of the scheduling request as the first set, selectingcontrol channel(s) associated with the condition as the first set, orselecting specific control channel(s) regardless of numerology and/orTTI information carried by the transmission of the scheduling request.

In one embodiment, at least one of the multiple downlink control channelcould schedule data transmission on all numerologies, on one or multiplenumerologies, or only on specific numerology. The at least one of themultiple downlink control channel could also schedule sidelinktransmission.

FIG. 45 is a flow chart 4500 according to one exemplary embodiment of aUE, wherein the UE is allocated with multiple SR configurations by anetwork node. In step 4505, the UE triggers a first SR related to afirst SR configuration of the multiple SR configurations. In step 4510,the UE performs a first SR transmission to the network node according tothe first SR configuration. In step 4515, the UE triggers a second SRrelated to a second SR configuration of the multiple SR configurations,wherein the second SR is not triggered by uplink data arrival. In step4520, the UE performs a second SR transmission to the network nodeaccording to the second SR configuration.

In one embodiment, the first SR could be triggered by uplink dataarrival (e.g. a regular BSR), a sidelink BSR (e.g. regular sidelinkBSR), a timer controlled based MAC control element, or a new MAC CEwhich is different from any uplink MAC CE listed in 3GPP TS 36.321.

In one embodiment, the second SR could be triggered by a sidelink BSR(e.g. regular sidelink BSR), a timer controlled based MAC controlelement, or a new MAC CE (which is different from any uplink MAC CElisted in 3GPP TS 36.321.

In one embodiment, the UE could stop performing a third SR transmissionto the network node according to the first SR configuration of themultiple SR configurations after the second SR is triggered. The UEcould decide to perform the second SR transmission according to thesecond SR configuration based on prioritization rule in LCP procedure,to the second SR configuration based on latency requirement of MAC CEtriggering the second SR, or to the second SR configuration, if thesecond SR is triggered by a sidelink BSR, wherein the sidelink BSR isfor reporting data belonging to a logical channel with priority higherthan a threshold.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UEwherein the UE is allocated with multiple SR configurations by a networknode, the device 300 includes a program code 312 stored in the memory310. The CPU 308 could execute program code 312 to enable the UE (i) totrigger a first SR related to a first SR configuration of the multipleSR configurations, (ii) to perform a first SR transmission to thenetwork node according to the first SR configuration, (iii) to trigger asecond SR related to a second SR configuration of the multiple SRconfigurations, wherein the second SR is not triggered by uplink dataarrival, and (iv) to perform a second SR transmission to the networknode according to the second SR configuration. Furthermore, the CPU 308can execute the program code 312 to perform all of the above-describedactions and steps or others described herein.

FIG. 46 is a flow chart 4600 according to one exemplary embodiment of aUE, wherein the UE is allocated with multiple SR configurations by anetwork node. In step 4605, the UE triggers a first SR related to afirst SR configuration of the multiple SR configurations, wherein thefirst SR is not triggered by uplink data arrival. In step 4610, the UEperforms a first SR transmission to the network node according to thefirst SR configuration. In step 4615, the UE triggers a second SRrelated to a second SR configuration of the multiple SR configurations.In step 4620, the UE performs a second SR transmission to the networknode according to the second SR configuration.

In one embodiment, the first SR could be triggered by a sidelink BSR(e.g. regular sidelink BSR), a timer controlled based MAC controlelement, or a new MAC CE (which is different from any uplink MAC CElisted in 3GPP TS 36.321.

In one embodiment, the second SR could be triggered by a sidelink BSR(e.g. regular sidelink BSR), a timer controlled based MAC controlelement, a new MAC CE which is different from any uplink MAC CE listedin 3GPP TS 36.321, or an uplink data arrival (e.g. a regular BSR).

In one embodiment, the UE could stop performing a third SR transmissionto the network node according to the first SR configuration of themultiple SR configurations after the second SR is triggered. The UEcould also decide to perform the second SR transmission according to thesecond SR configuration based on prioritization rule in LCP procedure,to the second SR configuration based on latency requirement of MAC CEtriggering the second SR, or to the second SR configuration, if thesecond SR is triggered by a sidelink BSR, wherein the sidelink BSR isfor reporting data belonging to a logical channel with priority higherthan a threshold.

In one embodiment, the first SR configuration and the second SRconfiguration could be for requesting resource on different numerologiesand/or TTI durations. Furthermore, the resource indicated by the firstSR configuration and resource indicated by the second SR configurationcould be on different cells. In addition, the resource indicated by thefirst SR configuration and resource indicated by the second SRconfiguration could be on different numerologies and/or TTI durations.

Referring back to FIGS. 3 and 4, in one exemplary embodiment of a UEwherein the UE is allocated with multiple SR configurations by a networknode, the device 300 includes a program code 312 stored in the memory310. The CPU 308 could execute program code 312 to enable the UE (i) totrigger a first SR related to a first SR configuration of the multipleSR configurations, wherein the first SR is not triggered by uplink dataarrival, (ii) to perform a first SR transmission to the network nodeaccording to the first SR configuration, (iii) to trigger a second SRrelated to a second SR configuration of the multiple SR configurations,and (iv) to perform a second SR transmission to the network nodeaccording to the second SR configuration. Furthermore, the CPU 308 canexecute the program code 312 to perform all of the above-describedactions and steps or others described herein.

Various aspects of the disclosure have been described above. It shouldbe apparent that the teachings herein may be embodied in a wide varietyof forms and that any specific structure, function, or both beingdisclosed herein is merely representative. Based on the teachings hereinone skilled in the art should appreciate that an aspect disclosed hereinmay be implemented independently of any other aspects and that two ormore of these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. As an exampleof some of the above concepts, in some aspects concurrent channels maybe established based on pulse repetition frequencies. In some aspectsconcurrent channels may be established based on pulse position oroffsets. In some aspects concurrent channels may be established based ontime hopping sequences. In some aspects concurrent channels may beestablished based on pulse repetition frequencies, pulse positions oroffsets, and time hopping sequences.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, processors, means, circuits, and algorithmsteps described in connection with the aspects disclosed herein may beimplemented as electronic hardware (e.g., a digital implementation, ananalog implementation, or a combination of the two, which may bedesigned using source coding or some other technique), various forms ofprogram or design code incorporating instructions (which may be referredto herein, for convenience, as “software” or a “software module”), orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentdisclosure.

In addition, the various illustrative logical blocks, modules, andcircuits described in connection with the aspects disclosed herein maybe implemented within or performed by an integrated circuit (“IC”), anaccess terminal, or an access point. The IC may comprise a generalpurpose processor, a digital signal processor (DSP), an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) or other programmable logic device, discrete gate or transistorlogic, discrete hardware components, electrical components, opticalcomponents, mechanical components, or any combination thereof designedto perform the functions described herein, and may execute codes orinstructions that reside within the IC, outside of the IC, or both. Ageneral purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

It is understood that any specific order or hierarchy of steps in anydisclosed process is an example of a sample approach. Based upon designpreferences, it is understood that the specific order or hierarchy ofsteps in the processes may be rearranged while remaining within thescope of the present disclosure. The accompanying method claims presentelements of the various steps in a sample order, and are not meant to belimited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with theaspects disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module (e.g., including executable instructions and relateddata) and other data may reside in a data memory such as RAM memory,flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a harddisk, a removable disk, a CD-ROM, or any other form of computer-readablestorage medium known in the art. A sample storage medium may be coupledto a machine such as, for example, a computer/processor (which may bereferred to herein, for convenience, as a “processor”) such theprocessor can read information (e.g., code) from and write informationto the storage medium. A sample storage medium may be integral to theprocessor. The processor and the storage medium may reside in an ASIC.The ASIC may reside in user equipment. In the alternative, the processorand the storage medium may reside as discrete components in userequipment. Moreover, in some aspects any suitable computer-programproduct may comprise a computer-readable medium comprising codesrelating to one or more of the aspects of the disclosure. In someaspects a computer program product may comprise packaging materials.

While the invention has been described in connection with variousaspects, it will be understood that the invention is capable of furthermodifications. This application is intended to cover any variations,uses or adaptation of the invention following, in general, theprinciples of the invention, and including such departures from thepresent disclosure as come within the known and customary practicewithin the art to which the invention pertains.

What is claimed is:
 1. A method of a User Equipment (UE), wherein the UEis allocated with multiple Scheduling Request (SR) configurations,comprising: starting a timer upon sending a first Medium Access Control(MAC) control element, wherein the first MAC control element istriggered due to data available for transmission; triggering a secondMAC control element in response to the timer expiry; selecting a firstSR configuration among the multiple SR configurations; and transmittinga SR based on the first SR configuration of the multiple SRconfigurations.
 2. The method of claim 1, wherein the SR is triggeredfor the second MAC control element.
 3. The method of claim 1, whereinthe timer is a retxBSR-Timer, and wherein there are multiple logicalchannels still having data available for transmission when the timerexpires.
 4. The method of claim 1, wherein the first and second MACcontrol elements are BSR (Buffer Status Report).
 5. The method of claim1, wherein the first SR configuration is associated with a highestpriority logical channel determined by comparing priorities of each ofthe multiple logical channels.
 6. The method of claim 1, wherein thefirst SR configuration is associated with the highest priority logicalchannel based on an identity of the highest priority logical channel. 7.The method of claim 1, further comprising triggering the first MACcontrol element if the UE has data for any logical channels that belongto a Logical Channel Group.
 8. A User Equipment (UE), comprising: amemory; and a processor operatively coupled to the memory, wherein theprocessor is configured to execute a program code to: start a timer uponsending a first Medium Access Control (MAC) control element, wherein thefirst MAC control element is triggered due to data available fortransmission; trigger a second MAC control element in response to thetimer expiry; select a first Scheduling Request (SR) configuration amongmultiple SR configurations; and transmit a SR based on the first SRconfiguration of the multiple SR configurations.
 9. The UE of claim 8,wherein the SR is triggered for the second MAC control element.
 10. TheUE of claim 8, wherein the timer is a retxBSR-Timer, and wherein thereare multiple logical channels still having data available fortransmission when the timer expires.
 11. The UE of claim 8, wherein thefirst and second MAC control elements are BSR (Buffer Status Report).12. The UE of claim 8, wherein the first SR configuration is associatedwith a highest priority logical channel determined by comparingpriorities of each of the multiple logical channels.
 13. The UE of claim8, wherein the first SR configuration is associated with the highestpriority logical channel based on an identity of the highest prioritylogical channel.
 14. The UE of claim 8, wherein the processor is furtherconfigured to execute a program code to trigger the first MAC controlelement if the UE has data for any logical channels that belong to aLogical Channel Group.
 15. A method of a User Equipment (UE), whereinthe UE is allocated with a plurality of Scheduling Request (SR)configurations, comprising: starting a timer upon sending a first MediumAccess Control (MAC) control element, wherein the first MAC controlelement is triggered due to data available for transmission; triggeringa second MAC control element in response to the timer expiry; selectinga first SR configuration among the plurality of SR configurations; andtransmitting a SR based on the first SR configuration of the pluralityof SR configurations.
 16. The method of claim 15, wherein the SR istriggered for the second MAC control element.
 17. The method of claim15, wherein the timer is a retxBSR-Timer.
 18. The method of claim 15,wherein the first and second MAC control elements are BSR (Buffer StatusReport).
 19. The method of claim 15, wherein the first SR configurationis associated with a highest priority logical channel determined by anidentity.
 20. The method of claim 15, further comprising triggering thefirst MAC control element if the UE has data for any logical channelsthat belong to a Logical Channel Group.